Minor issue with the presets of iD

I have recently noted 2 issues with the presets of iD.

The preset for restrooms offers the option flush - pit - latrine - chemical and does not allow any manual entry. How about composting toilets which are very common on campgrounds in national parks and the like? There are the values composting and dry_toilet (and problably more) in taginfo but iD would not let you use those.

When mapping a charging station and adding a brand like ChargeOne iD tells you that is not sufficient and wants you to additionally tag name=ChargeOne. That name seems to be very important, because if you don’t obey you will get another warning when uploading your CS that the charging station is missing an attribute.

This is weird, as a charging station is not an individual business like a supermarket or a filling station but just a technical device and as such normally does not have an individual name. It is nothing but a big power socket and I have never seen a power socket having an individual name so far. If someone wants to add a name to such a device manually it’s one thing, but the editor should not enforce something like that imo.

Anything we should or can do about that?

Ping @Mateusz_Konieczny :waving_hand:t2:

A charging station (amenity=charging_station) is an… amenity.

What you describe as big plugs are the man_made=charge_point.

I think this is a usefull distincton.

So, a location which is an amenity, usefull as POI for drivers needs a name or not?

1 Like

Sure, and it consists of some big power sockets and a few parking places. Does that need a name? Is the power you get from one charging station different from the power drawn form another one? All the relevant information are given by the specific tags we are adding and additionally we are tagging the brand for those who think this is important. So for what do we need an additional name when the name is identical to the brand anyhow? It is just a redundant data field without any additional value.

1 Like

not. There are many amenities that do not have a name, what is essential is the type and a location.

2 Likes

So, gas stations need a name? I guess not.
Supermarkets of a brand? No?

I always see name on those two amenities.

Naming of charging stations in Greece is usually the place that hosts the amenity.
And it’s very usefull with routing software.

A fuel station and a supermarket are individual businesses. A charging station is not. It is a simple technical installation. Anyhow I did not say that it should not be allowd to tag a name if someone finds that useful, I just said that the editor should not enforce it:

7 Likes

I am not saying it must be mandatory for the name. It’s up to the local community the usage of name.
I am stating the usefulness of a proper name.
The providers in Eastern Europe where i have driving exprerience always have names as i pointed earlier for their locations.
In Greece i even include multilingual name for each station..

Nr. 2 has probably nothing to do with iD-Editor itself. The problem seems to be that NSI (which iD derives the “expected” values from) has a suspicous name chargeone NSI

If it shouldn’t have a name then that can only be fixed by changing the NSI template.

Yes, it is something to be reported in NSI first.

(Though I would not go as far to call it nothing to do with iD, after all iD has chosen to use NSI and continues using it)

3 Likes

In the case of charging stations the name is just a copy of the brand. Or do you have charging stations in Greece which have a brand like “ChargOne” and a separate name like “Nikos”? If brand and name are identical, the name does not add any value.

I am not a user of NSI, don’t have an NSI account and no idea how to make them change one of their presets. Also I believe they would not care if one OSM user asks them for a change. In such cases some kind of support would be quite helpful, I guess.

Then there is the first issue with the restroom presets. How to address that?

Hi, Mikke!

Whenever possible, I always go for the easiest option: if I want to make an entry in iD that isn’t included as a preset – like the four blue presets you mentioned – I just click on the first suggestion that comes up

and then edit it in the properties. You can enter anything there, including composting.

Just as an aside: there are already six variants that appear ‘by default’ there.

Greets

Andreas

You need GitHub account, they are at GitHub - osmlab/name-suggestion-index: Canonical common brand names, operators, transit, and flags for OpenStreetMap. · GitHub - and currently if you use iD you use also NSI.

If you really want to avoid this - can you link specific avoided OSM object where it is happening?

(In general I have this thread bookmarked and will look more into it when I have access to computer)

Thanks for the tip. That’s exactly how I do it, except that it didn’t work when I tried to map the composting toilet in question. The system displayed exactly the four values I mentioned. I couldn’t manually add a new one, nor could I overwrite any of them.

It is still the same now, and no difference if I use the english or german version of the editor. No idea what is wrong here.

Way: 1543335711 | OpenStreetMap

suggested update = adding name

When ignoring another error message follows when uploading :roll_eyes:

1 Like

I’ve just built one in my garden (as a test) – no problem at all!

What are you doing differently? :thinking:

…and if you upload it anyway, you’ll end up with a permanent ‘mark of shame’ :flushed_face: on your HDYC page!

Screenshot 2026-08-31 at 15-09-39 How did you contribute to OpenStreetMap
(That’s down to my early days – something I’ll just have to put up with…)

1 Like

Thanks for the hint, I have never had a look into these stats before. Just checked it now and have to admit that I have already collected 244 of these marks of shame … :joy: … I hope they will not block my account when I get close to 500!

1 Like

Is there really consensus against using both brand= and name= for shops/fuel stations/charging stations?

Or no consensuses either way?

I thought that standard is to use both (and I use both or only name= when I map manually)