#17034 closed enhancement (fixed)
Add support for power=connection
Reported by: | Penegal | Owned by: | team |
---|---|---|---|
Priority: | normal | Milestone: | 21.12 |
Component: | Internal preset | Version: | |
Keywords: | power connection preset warning validation | Cc: | Gazer75 |
Description (last modified by )
There happens that crossing power lines are connected with one another without any supporting pole or tower, such as on the attached picture. In this case, the lines share a node tagged power=connection
, but JOSM has no support of this configuration: it has no such preset, and warns about power line nodes without power=(pole|tower)
. Could this preset be added and the relevant warning adapted to not show when the node is tagged power=connection
?
Attachments (3)
Change History (35)
by , 6 years ago
Attachment: | Example.png added |
---|
comment:1 by , 6 years ago
Description: | modified (diff) |
---|
follow-up: 4 comment:2 by , 6 years ago
Nice one
power=connection haven't been reviewed yet.
It has been part of a huge (rejected) proposal in 2014 : https://wiki.openstreetmap.org/wiki/Proposed_features/Power_paths_refinement
Despite it is currently used about 1000 times, I'm not sure to add it as a preset.
Nevertheless, JOSM shouldn't warn users when two power=* lines connect each other.
The warning should raise if and only if the node is shared by both power and non-power objects or standalone in a single line.
We can find connection nodes with power=switch in substations for instance
Hope it helps
comment:3 by , 6 years ago
Component: | Core → Internal preset |
---|---|
Milestone: | → 18.12 |
comment:4 by , 6 years ago
Replying to francois.lacombe:
I'm not sure to add it as a preset.
Is there a reason? The tag seems fine to me.
comment:5 by , 6 years ago
It is not currently documented on wiki.
Despite the idea sounds good, if there is no connection, then there should be no shared node between nodes.
connection=* (especially connection=no) is find to say that several lines sharing the same pole aren't connected.
Additional design should be done with those two tags.
I fully agree on the warning anyway
comment:6 by , 6 years ago
Milestone: | 18.12 → 19.01 |
---|
comment:7 by , 6 years ago
Milestone: | 19.01 → 19.02 |
---|
comment:8 by , 6 years ago
Milestone: | 19.02 → 19.03 |
---|
comment:9 by , 6 years ago
Milestone: | 19.03 → 19.04 |
---|
comment:10 by , 6 years ago
Milestone: | 19.04 → 19.05 |
---|
follow-up: 29 comment:12 by , 5 years ago
Milestone: | 19.05 |
---|
comment:13 by , 5 years ago
Thank you Klumbumbus
I'd be in favour of 3rd icon from your proposal
First two, with straight connections may let mapper think they refer to bundles link like here : https://wiki.openstreetmap.org/wiki/File:JP_Power_Wires_Fivefold.JPG
Regarding power=connection vs connection=* I think both should be valid, depending on the previous usage of power=* for another value (like poles)
comment:14 by , 5 years ago
Replying to Klumbumbus:
In 15088/josm: ... add svn:mime-type of images
Please check images/data/imagery/photo.svg again. This icon needs 80% of the help browser screen and is currently not seen in the Imagery menu. The other svg images are also very larrge in the help browser.
by , 5 years ago
Attachment: | photo-vs-other.png added |
---|
comment:16 by , 5 years ago
follow-up: 18 comment:17 by , 3 years ago
numbers are still low resp. minimal for power=connection
and connection=*
Regarding power=connection
my major concern is the missing wiki page.
comment:18 by , 3 years ago
Replying to skyper:
Regarding
power=connection
my major concern is the missing wiki page.
See: https://wiki.openstreetmap.org/wiki/Tag:power%3Dconnection
comment:20 by , 3 years ago
Cc: | added |
---|
comment:21 by , 3 years ago
I'm in favor of adding power=connection now. The wiki page is present and the number grows constantly. connection=* on the other hand has still a very low count.
I can do the peset and mappaint part, but someone else needs to adapt the validator test (i.e. don't warn about power=connection on power intersection nodes and adapt the warning message). This also interferes with the patch in #20716.
follow-ups: 24 25 comment:22 by , 3 years ago
I think fixing the validator only requires to add connection
to either POWER_TOWER_TAGS
or POWER_ALLOWED_TAGS
.
comment:24 by , 3 years ago
Replying to skyper:
I think fixing the validator only requires to add
connection
to eitherPOWER_TOWER_TAGS
orPOWER_ALLOWED_TAGS
.
I haven't looked at the code, so can't say whether what you suggest will have the desired effect or not, but I see some potential pitfalls to keep in mind.
One is that power=connection
likely shouldn't be considered on par with tower
or pole
in all situations. For instance, it makes little sense on a single line. My understanding of the tag is that is should exclusively be present on line crossings.
So, if you replace a power=tower
with a power=connection
on a single line, that should probably raise a warning.
This would have the added benefit of catching issues caused by having a valid line crossing with a connection and then deleting one of the connected lines.
follow-up: 26 comment:25 by , 3 years ago
I removed most false warnings for power=connection
in the validator, that's all for now. No patch yet. What else is needed?
comment:26 by , 3 years ago
comment:27 by , 3 years ago
Can be done before, as just adding the "connection"
string here silences the "Missing power tower/pole within power line" warning.
-
src/org/openstreetmap/josm/data/validation/tests/PowerLines.java
44 44 static final Collection<String> BUILDING_STATION_TAGS = Arrays.asList("transformer_tower"); 45 45 /** Values for {@code power} key interpreted as allowed power items */ 46 46 static final Collection<String> POWER_ALLOWED_TAGS = Arrays.asList("switch", "transformer", "busbar", "generator", "switchgear", 47 "portal", "terminal", "insulator" );47 "portal", "terminal", "insulator", "connection"); 48 48 49 49 private final Set<Node> badConnections = new LinkedHashSet<>(); 50 50 private final Set<Node> missingTowerOrPole = new LinkedHashSet<>();
comment:28 by , 3 years ago
Milestone: | → 21.11 |
---|
Example of connections