Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Power outlet (sockets) #1468

Open
2hu4u opened this issue Mar 3, 2025 · 2 comments
Open

Power outlet (sockets) #1468

2hu4u opened this issue Mar 3, 2025 · 2 comments

Comments

@2hu4u
Copy link

2hu4u commented Mar 3, 2025

OSM Tag(s)

socket:*=yes

How would you like this tag to see supported?

As a Preset

Label

Power Outlet - ([ISO 3166-2 code])

Aliases

power point; power supply

Terms

No response

Link to OSM Wiki page

https://wiki.openstreetmap.org/wiki/Key:socket:*

Status of the Tag

In Use

Usage of the tag

Over 15000

Suggested Icon

See body text

Replaces other Tag?

No response

Regional Tag?

global but with different presets per region

Further Information

Rationale

I propose adding a preset for common types of power outlet sockets. This will encompass the family of keys relating to domestic power outlets: socket:*. Currently, there is a large barrier towards the uptake of mapping power outlets, because keys of format socket:* have cryptic and difficult-to-remember names such as "typeE", "as3112", "bs1363", "nema_5_15" amongst others. As a result, public power outlets are a useful amenity that are largely unmapped compared to similar amenities such as drinking water and EV charging stations because the tagging is difficult. I find that without this preset, I have to dig through a large list of international sockets (that include all the electric vehicle charging sockets) on the OSM Wiki every time.

Tag usage and competing tags

There are a few similar (competing?) tags for domestic power outlets - the main two are amenity=power_supply (about 600 uses) and power=outlet (about 300 uses), with a more general power_supply=yes having about 36000 uses. Luckily, there is general concensus amongst all of these that the socket:* key group be used to specify the socket type. Therefore I don't think this will be problematic or favour any of the competing tags. Overall, the socket:* key group has about 15000 uses pertaining to domestic power outlets and close to 100K for electric vehicle charger sockets.

Regional tagging example

I suggest regional presets use the ISO 3166-2 country code. In Australia, there should be a regional preset such as "Power Outlet (AU)" for a domestic single phase outlet specified by the key socket:as3112. This could be expanded as necessary per country, such as socket:nema_5_15 for North America, socket:bs1363 for UK/Hong Kong etc.
In some cases, there may be an identical tagging structure for a preset called "Power Outlet (NZ)" which also uses socket:as3112.
In some cases, there will be multiple outlet styles used in a country; for example "Power Outlet (AU - 3 phase)" may be a preset for socket:as3123_5pin in Australia. In China, there are 3 commonly used outlet types that would need consideration.

Icon example

The preset should have an icon that is easy for the mapper to recognise. Power outlets are generally easy to recognise visually. The below example is a mockup for socket:as3112 and socket:as3123_5pin which are commonly found in Australia;

Image

Suggested tagging and form fields structure

  • The key type of socket: should be a dropdown menu, but have a default subkey as per the regional preset
  • The value of socket:*= should be yes by default, but perhaps should include a spinbox form field that allows the user to enter the number of sockets present.

Additionally;

  • power_supply=yes
  • power_supply:voltage=* (menu)
  • locked=* checkbox
  • access=* field
@2hu4u 2hu4u added the needs-triage This is a fresh issue which has not yet been looked over by the maintainers of this repository. label Mar 3, 2025
@k-yle k-yle added new-preset new-field and removed needs-triage This is a fresh issue which has not yet been looked over by the maintainers of this repository. labels Mar 4, 2025
@k-yle
Copy link
Collaborator

k-yle commented Mar 4, 2025

Without making any code changes to iD, it's only possible to support a very basic implementation:

  • socket:*=yes
  • socket:*=1
  • *:current, *:voltage etc. with default values
  • ❌ limiting field values by country

With these limitations in mind, a basic version has already been implemented here:
Image

It's worth considering whether this primitive implementation should be added now, or if we should wait until a proper editor for this field can be built.

@2hu4u
Copy link
Author

2hu4u commented Mar 4, 2025

Thanks for the response. The primitive implementation looks great. My suggestion was an ideal case, but for now that will achieve most of my objectives for the request.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants