Modify ↓
#19216 closed defect (othersoftware)
Preset of "Pipeline" creates tag that is later flagged as inconsistent in iD
Reported by: | Owned by: | team | |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | Internal preset | Version: | tested |
Keywords: | template_report | Cc: |
Description
What steps will reproduce the problem?
- Create a new line and use preset "Man made/Man made/Pipeline"
- Save and upload
- Select the new way in iD
- It will be flagged as "<variable> has incomplete tags"
- iD shows "Suggested updates: + layer=-1"
What is the expected result?
JOSM does not miss a tag
What happens instead?
Flagged by iD as error
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: 2020-04-06 02:17:07 +0200 (Mon, 06 Apr 2020) Build-Date:2020-04-06 00:18:43 Revision:16239 Relative:URL: ^/trunk Identification: JOSM/1.5 (16239 en_AU) Windows 7 64-Bit OS Build number: Windows 7 Professional (7601) Memory Usage: 1193 MB / 1820 MB (268 MB allocated, but free) Java version: 1.8.0_251-b08, Oracle Corporation, Java HotSpot(TM) 64-Bit Server VM Screen: \Display0 1920x1200, \Display1 1920x1200 Maximum Screen Size: 1920x1200 Dataset consistency test: No problems found Plugins: + Mapillary (1.5.22) + apache-commons (35362) + apache-http (35092) + imagery_offset_db (35405) + javafx-windows (35375) + jna (35092) + turnrestrictions (35405)
Attachments (0)
Change History (2)
comment:1 by , 5 years ago
Resolution: | → othersoftware |
---|---|
Status: | new → closed |
comment:2 by , 5 years ago
Component: | Core → Internal preset |
---|
Note:
See TracTickets
for help on using tickets.
There is no need for a layer tag for man_made=pipeline. In fact, the wiki page suggests
location
andlayer
is not mentioned. In general, it is discouraged to tag long ways withlayer
instead you may split it to only uselayer
on the needed, small segment.Nothing wrong in JOSM but, please, report the issue to iD where it needs to be fixed.