I am quite proud how high my counts are. And large part of Osmose complaints is misleading nonsense, the same for chunk of iD ones.
Sadly I see that Osmose ones are going down for me, I need to find way to bring back old glory.
(Also, HDYC should not display those or should have disclaimer how QA tools are often wrong)
(Yes, I reported some bugs and made some PRs to Osmose, last round remains unresolved by maintainers)
There is no argument about shops and fuel stations. As I said above shops and fuel stations are individual businesses. Those usually have names, although one could argue that name=brand is nonsene anyhow, but that is not the point here.
A charging station is no individual business. It is a simple technical installation and there was no NSI request to set name=brand until very recently. At least I did not experience one and I have mapped quite some charging station earlier. Technical objects like charging stations, power distributors or vending machines usually do not have names. If they have, one may tag those manually but a NSI request to set name=brand is not necessary for sure.
Btw. there was a discussion about tagging opening hours and names (among other things) to charging stations not long ago:
How do I (legally) map the opening hours of charging stations?
and there was some consensus that most of them do not have individual names.
No idea. I have not experienced any restriction when trying to use the preset values until now.
What I can do is choose one of the 4 offered values, then go to the properties box and change that one manually to the correct value there.
As that would be a bit complicated for a new user it would be great if this little bug could be identified and corrected.
You’ll come across these restrictions in some entries highlighted in blue: have a click through the menu under ‘Parking’ or ‘Fire hydrants’. I don’t think this is necessary, but it’s presumably intended to stop ‘newcomers’ from entering any nonsense. It’s a futile effort, mind you, but we know how to get round it. Incidentally, I think ‘toilets:disposal=composting’ is more straightforward than the solution mentioned in the wiki – ‘toilets:disposal=pitlatrine + composting=yes’ – which, to me (as is so often the case), seems too cumbersome.
Wiki at Tag:amenity=toilets - OpenStreetMap Wiki advises using different tagging
Iff this composting value is established and preferable it should be mentioned at wiki
Haha. I got that beat, but only because iD’s Cycle & Foot preset is not according to community consensus (https://github.com/openstreetmap/id-tagging-schema/pull/1792).
You are right. I did not note this restriction earlier because either I use one of the offered values or my own preset containing all the tags for one object so I don’t need to click through the attributes one by one. Thanks for clarifying. Funny enough though that the preset box offers only 4 options whereas the drop-down selector in the properties offers 6. Anyhow, as you said wie know how to deal with it … 
You are right, I did not read the wiki cause a composting toilet is a simple thing to map and I did not expect such a nonsense combination like toilets:disposal=pitlatrine + composting=yes to be documented in the wiki.
A composting toilet has not much in common with a pitlatrine. It is a completely different approach and I don’t see any reason why we should not tag it without using the deviation via pitlatrine.
Acc. to taginfo there are
toilets:disposal=composting (48 + compost 12)
toilets:disposal=dry_toilet (452)
Should we mention these tags in the wiki as alternative?
maybe composting property is orthogonal and applicable to other toilet types?
(no idea, if clear conclusion is reached feel free to ping me again, or even better: open issue at iD tagging schema repository)
You mean I should open a topic here in the forum about this issue, correct? That would not be a problem.
Meant GitHub tagging schema repository at Issues · openstreetmap/id-tagging-schema · GitHub
Got eaten by browser, I edited the post now
You can also open thread and hope that someone will see & agree with you & and open the issue. I am doing it often but I will not precommit to doing it for all eternity.
Sorry to keep you busy. I am not familiar at all with these Github issues, iD tagging scheme repository, NSI stuff and the like and I’d say one cannot expect that from every mapper.
I have seen that the wiki page for amenity:toilets contains 7 documented values for toilets:disposal out of which only 4 are offered in the presets. I always thought the presets are automatically updated from the wiki (sorry for being kind of stupid). Now I realize this requires another step … 
Mapping is one thing, discussing issues in the forum and editing or creating wiki pages another one and I feel I am spending too much time with such issues already. GitHub + Co is the next level and I don’t think I want to dive into it, spending even more of my limited OSM time there. And sure, I really understand that you don’t want to keep doing this for others forever, it’s not your job either.
So I think I will shift one gear down, forget about such minor issues, use the tag I feel fits best for a certain case and go on mapping. Toilet case closed.
On the other hand if anyone would be interested in dealing with wiki/tagging/GitHub and who knows what else: feedback is very welcome!
I am trying to catch directly actionable ones but this seems to require research/documenting new (or existing) tagging schema/maybe also discussing it.
I have now created a topic for the composting toilets although the toilet case had been closed already … 
if it was close due to lack of documentation/indication of it being supported by OSM tagging consensus then discussing it may enable reopening it
Carrying on with this topic, the iD preset gives the option of tagging toilets as “Pit Latrine”, but that then appears on OSM as “pitlatrine” i.e. one word, not two.
What would we need to do to fix this, as it should be two words?
something seems missing here?
I think it refers to pit latrine which is written in the preset in 2 words, which is correct imo:
Whereas the tag which is set reads ‘toilets:disposal=pitlatrine’. Pitlatrine in one word may cause confusion, as you could see in the parallel thread I opened for ‘toilets:disposal=composting’ as linked above.
oh
then it is caused by fact that tag descriptions shown by iD are in this case shown in English rather than showing raw tag values
when iD shows raw tag values it shows in this characteristic black font
when translated it is in this bluish font
So how do we fix it?
Raise a Github issue?
Oh, incidentally, I quoted the word earlier as < > which obviously made them disappear for some reason?