Skip to content

Add field for line_arrangement, add presets for power=insulator and power=terminal #1042

Closed
arch0345 wants to merge 3 commits intoopenstreetmap:mainfrom
arch0345:line_arrangement
Closed

Add field for line_arrangement, add presets for power=insulator and power=terminal #1042
arch0345 wants to merge 3 commits intoopenstreetmap:mainfrom
arch0345:line_arrangement

Conversation

@arch0345
Copy link
Copy Markdown
Contributor

@arch0345 arch0345 commented Oct 28, 2023

Adds a field for line_arrangement=*, which was approved back in July. This PR also adds presets for power=insulator and power=terminal and adds translatable options for Line Attachment and Line Management fields

@github-actions
Copy link
Copy Markdown

🍱 Preview the tagging presets of this pull request here: https://pr-1042--ideditor-presets-preview.netlify.app/id/dist/#locale=en.

@tyrasd tyrasd added new-field create a new field (see add-field for cases where field from presets is added to new entries) new-preset labels Nov 20, 2023
@tyrasd tyrasd changed the title Add field for line_arrangement Add field for line_arrangement, add presets for power=insulator and power=terminal Nov 20, 2023
Copy link
Copy Markdown
Member

@tyrasd tyrasd left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please find some inline comments below.

Generally speaking, I'm struggling a little bit to see the benefit these domain-specific attributes/tags provide in a general purpose OSM editor. Especially when it comes to translatable values there might also be downsides:

  • for volunteers translating on transifex (which I assume are typically not trained electrical engineers), it takes valuable time and effort to fully comprehend these tagging schemas and potentially even more time and effort to find proper translations
  • it would be easy to introduce a few small mistakes when translating those terms, which could result in a large number of mappers inadvertently choosing wrong tag values
  • if the fields were left "raw", it would be implicitly a bit more obvious that one should consult the wiki before mapping these attributes

What do you think?

Comment on lines +6 to +9
"suspension": "Suspension",
"anchor": "Anchor",
"pin": "Pin",
"pulley": "Pulley"
Copy link
Copy Markdown
Member

@tyrasd tyrasd Nov 20, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If we were to go with translatable strings for these tags, I'd prefer if these would be a bit more verbose. I assume these are technical terms, but for a general mapper, they are not particularly helpful – if one must read the wiki to interpret the values, the raw tag values work just as well.

Perhaps something along these lines would work?

Suggested change
"suspension": "Suspension",
"anchor": "Anchor",
"pin": "Pin",
"pulley": "Pulley"
"suspension": "Suspended line",
"anchor": "Straight tension sets",
"pin": "Supports underneath the line",
"pulley": "Pulley"

Comment on lines +6 to +12
"straight": "Straight",
"branch": "Branch",
"split": "Split",
"transpose": "Transpose",
"cross": "Cross",
"transition": "Transition",
"termination": "Termination"
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

see above, perhaps something like this could work:

Suggested change
"straight": "Straight",
"branch": "Branch",
"split": "Split",
"transpose": "Transpose",
"cross": "Cross",
"transition": "Transition",
"termination": "Termination"
"straight": "Single line continues",
"branch": "Side line branches off",
"split": "Lines split towards different directions",
"transpose": "Line bundles are swapped",
"cross": "Lines cross without connecting",
"transition": "Location changes",
"termination": "Line stops"

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"straight": "Line continues", no need to have a single line

],
"moreFields": [
"height",
"line_arrangement",
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

FWIW, the combination power=insulator + line_arrangement has (currently) zero uses in OSM: https://overpass-turbo.eu/s/1DGp

🤷

Copy link
Copy Markdown
Contributor

@flacombe flacombe Nov 20, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes but it's a valid combination

https://wiki.openstreetmap.org/wiki/File:Power_portal_substation_transition.jpg => horizontal arranged insulator (with a portal mapped as a way)
We may find semi_horizontal suspension portals as well, I don't have picture currently.

Comment thread data/fields/line_arrangement.json Outdated
Comment thread data/fields/line_arrangement.json Outdated
arch0345 and others added 2 commits November 20, 2023 10:57
Co-authored-by: Martin Raifer <martin@raifer.tech>
Co-authored-by: Martin Raifer <martin@raifer.tech>
@matkoniecz
Copy link
Copy Markdown
Collaborator

@arch0345 arch0345 marked this pull request as draft 2 years ago

do you plan on continuing it or should it be closed as an abandoned PR?

@flacombe
Copy link
Copy Markdown
Contributor

power=terminal preset is also discussed in #1637

@arch0345
Copy link
Copy Markdown
Contributor Author

Don't have any plans on working on this right now

@arch0345 arch0345 closed this Sep 14, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

new-field create a new field (see add-field for cases where field from presets is added to new entries) new-preset

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants