#10622 closed defect (fixed)
render barrier=yes as barrier
Reported by: | mkoniecz | Owned by: | team |
---|---|---|---|
Priority: | normal | Milestone: | 14.10 |
Component: | Internal mappaint style | Version: | |
Keywords: | template_report | Cc: |
Description
What steps will reproduce the problem?
- tag line as barrier=yes (unclear type of barrier on aerial images, recommended type of tagging in this situation, mentioned on wiki)
What is the expected result?
- Line will be rendered as a barrier.
What happens instead?
- Line is not rendered as a barrier.
See https://www.openstreetmap.org/way/307168742 for an example.
Repository Root: http://josm.openstreetmap.de/svn Build-Date: 2014-10-08 01:35:06 Last Changed Author: Don-vip Revision: 7608 Repository UUID: 0c6e7542-c601-0410-84e7-c038aed88b3b Relative URL: ^/trunk URL: http://josm.openstreetmap.de/svn/trunk Last Changed Date: 2014-10-08 00:01:23 +0200 (Wed, 08 Oct 2014) Last Changed Rev: 7608 Identification: JOSM/1.5 (7608 en) Linux Ubuntu 14.04.1 LTS Memory Usage: 435 MB / 889 MB (155 MB allocated, but free) Java version: 1.7.0_67, Oracle Corporation, Java HotSpot(TM) Server VM Dataset consistency test: No problems found Plugins: - ImportImagePlugin (30416) - OpeningHoursEditor (30609) - PicLayer (30436) - buildings_tools (30485) - continuosDownload (1412331234) - geotools (30569) - jts (30416) - log4j (30416) - notes (v0.9.4) - turnrestrictions (30651)
Attachments (1)
Change History (7)
by , 10 years ago
Attachment: | Selection_004.png added |
---|
comment:1 by , 10 years ago
Component: | Core → Internal mappaint style |
---|
comment:2 by , 10 years ago
Milestone: | → 14.10 |
---|
comment:3 by , 10 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
comment:4 by , 10 years ago
I do not like this change and we need a validator warning about barrier=yes
, now, like,
"
barrier=yes
is unspecific, please replaceyes
with a specific value".
Some notes:
- the value was added to the wiki without discussion just six month ago
- there exists no own wiki page
- if your aerial images are that bad, you can hardly determine barriers at all and definitely miss many entrances.
I did use barrier=yes
myself, in the beginning of my tagging, adding it to waterways and other primary features but meanwhile stop doing it as the information is mostly covered with the primary tag.
comment:5 by , 10 years ago
if your aerial images are that bad, you can hardly determine barriers at all
Untrue, see attached file - aerial images are really good. But it is really hard to decide whatever something is wall or fence.
In 7611/josm: