Modify

Opened 3 years ago

Closed 2 years ago

Last modified 2 years ago

#21836 closed enhancement (fixed)

voltage-high and voltage-low keys replacement on power transformers

Reported by: francois.lacombe Owned by: team
Priority: normal Milestone: 22.08
Component: Core validator Version:
Keywords: power, transformer, voltages Cc:

Description

Dear maintainers,

In #15367, deprecation of special voltages keys voltage-high and voltage-low has been forgotten.
It follows the approval of https://wiki.openstreetmap.org/wiki/Proposed_features/Transformer_extension_proposal in 2017

Wiki is up to date with dedicated pages for replacement guidelines.

Is it possible to raise a warning, at least like voltage=* in combination with power=transformer/transformer please?

By default, voltage-high and voltage-low are respectively replaceable by voltage:primary and voltage:secondary
When combined to transformer=generator, voltage-high and voltage-low are respectively replaceable by voltage:secondary and voltage:primary (primary and secondary are inverted).

Keep up with good work :)

Attachments (0)

Change History (15)

comment:1 by gaben, 3 years ago

Isn't the primary winding is on the input, while the rest is on the output side, regardless of the voltage level? So changing keys require a bit of luck to get it right.

Last edited 3 years ago by gaben (previous) (diff)

comment:2 by francois.lacombe, 3 years ago

That's right.
It's mostly correct to state voltage-high = voltage:primary, except in power plants with transformers used to step up voltage to transmit power over the grid (where voltage-low is the primary voltage).

transformer=generator can be added on step up transformer and then JOSM could adapt its fix recommendation.

JOSM could also propose to add transformer=generator when primary < secondary voltage, if available.

comment:3 by francois.lacombe, 3 years ago

https://wiki.openstreetmap.org/wiki/Key:voltage:primary

A good side improvement would be to warn about some voltage:primary (and respectively voltage:secondary, voltage:tertiary...) usage on following situations:

  • Used on areas, relations (wiki states it's only valid on nodes)
  • Missing required transformer=* key.

As to avoid situations like this one, using voltage:primary to distinguish substation's voltages.
https://www.openstreetmap.org/way/88462768

comment:4 by Klumbumbus, 2 years ago

In 18535/josm:

see #21836 - Add some power/voltage validation rules:

  • voltage:primary/secondary/tertiary without transformer
  • voltage:primary/secondary/tertiary on a way
  • voltage:primary/secondary/tertiary not in correct number format (should be in volts with no units/delimiter/spaces)
  • don't warn about unknown numeric values of voltage:primary/secondary/tertiary
  • transformer together with voltage on nodes
  • voltage:secondary is lower than voltage:primary on transformer=generator
  • deprecate voltage-high and voltage-low in favor of voltage:primary/secondary

in reply to:  2 ; comment:5 by Klumbumbus, 2 years ago

Replying to francois.lacombe:

JOSM could also propose to add transformer=generator when primary < secondary voltage, if available.

I think this is a bit risky, since the voltage:primary/secondary tags could be mixed up. Instead I added a warning when voltage:secondary is lower than voltage:primary on transformer=generator. Is the other way round also a safe error? i.e. voltage:secondary is higher than voltage:primary on a transformer=* which is not a transformer=generator

comment:6 by Klumbumbus, 2 years ago

Milestone: 22.07

Do you think something important was missing in r18535?

comment:7 by Klumbumbus, 2 years ago

In 18536/josm:

see #21836 - Improve error messages (use only key instead of whole tag)

comment:8 by skyper, 2 years ago

Milestone: 22.0722.08

22.07 was released but trac is not up to date.

in reply to:  8 ; comment:9 by taylor.smock, 2 years ago

Replying to skyper:

22.07 was released but trac is not up to date.

Yep. I think either stoecker/Don-vip have to close the milestone. Or someone else with the appropriate privileges. I did the release, but I cannot close milestones ( as specified on wiki:DevelopersGuide/Releasing ). It looks like someone has gone in and marked the milestone completed on the appropriate day.

in reply to:  9 comment:10 by Klumbumbus, 2 years ago

Replying to taylor.smock:

It looks like someone has gone in and marked the milestone completed on the appropriate day.

Yes that was me. Yesterday I marked it as completed on 2022-08-02.

in reply to:  5 comment:11 by francois.lacombe, 2 years ago

Hi all

That sounds really good to me, thank you!

Replying to Klumbumbus:

I think this is a bit risky, since the voltage:primary/secondary tags could be mixed up. Instead I added a warning when voltage:secondary is lower than voltage:primary on transformer=generator. Is the other way round also a safe error? i.e. voltage:secondary is higher than voltage:primary on a transformer=* which is not a transformer=generator

That's indeed relevant and safer.
Let this warning raises with "Primary < secondary MAY be wrong when no transformer=generator" instead of proposing transformer=generator.

comment:12 by francois.lacombe, 2 years ago

Depending on team planning and need to release quickly 22.08, it would be great to deal with #20421 that introduce changes on transformers presets as well.

I'll try to comit something in coming days if I manage to free a couple of hours.

comment:13 by Klumbumbus, 2 years ago

Resolution: fixed
Status: newclosed

I think this ticket is done. Further improvements see #20421 and #22200.

comment:14 by francois.lacombe, 2 years ago

Agreed, thank you everyone :)

comment:15 by skyper, 2 years ago

See #22639

Modify Ticket

Change Properties
Set your email in Preferences
Action
as closed The owner will remain team.
as The resolution will be set.
The resolution will be deleted. Next status will be 'reopened'.

Add Comment


E-mail address and name can be saved in the Preferences .
 
Note: See TracTickets for help on using tickets.