Yes, you are right. I was a too concise here.
I only described the highway=* tag, not the crossing=*, which is equal in both cases.

"There is no further tagging needed..." was meant to be a new paragraph addressing your question on how to make clear it is HAWK.

Hi,
you added tags like this one to more than 200 objects. Could you have a look and remove them?
extensions <extensions xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:ogr="http://osgeo.org/gdal" xmlns="http://www.topografix.com/GPX/1/1">
<ogr:Id>TM3</ogr:Id>
<ogr:Tipo>TM</ogr:Tipo>
<ogr:Cod>3.0</ogr:Cod>
<ogr:Norte>968187.0</ogr:Norte>
<o

Cheers, Jan

Hi,
you added some ways with only strange tags like this one:
way/514499767
Could you have a look and fix this?

Cheers, Jan

Hi,
it looks like this and another changeset added 51 objects with strange tags like these:

ADDRTYPE=SUBORD
FULLADDR=20 MALACHIGAN, CROISSANT DU
PI_MUNICIP=__AK2WLJ
POINT_X=383815.2027
POINT_Y=5034062.8701

Hi,
you added the key 'estd:' to various objects. This key is not yet used in any other place. I guess you should use "start_date" instead, which is used everywhere else.

Also, please use the Gregorian Calendar for dates - otherwise data can not be easily understood by any OSM tool.

Cheers, Jan

Hi,
you added the key 'estd:' to various objects. This key is not yet used in any other place. I guess you should use "start_date" instead, which is used everywhere else.

Also, please use the Gregorian Calendar for dates - otherwise data can not be easily understood by any OSM tool.

Cheers, Jan

Hi,
you added a new key here, and used several different spellings:

FR:grande_circulation
fr:grande_circulation
fr:grande_circulation_1

OSM Tags are case sensitive, could you change them to a common spelling? Additionally, we usually don't put a language code in front of a tag. It should be a country code (capital letters, 'FR') and is normally a suffix.

Cheers, Jan

Yes, this is a possible way.
a) if you use iD, check all tags again after snapping the node to the intersection - some of them are already tagged and this might cause iD to add wrong tags.

b) Are these traffic lights for pedestrians only or do they control the intersection as well?
node/4963108065
If only for pedestrians, use highway=crossing; if they control the whole intersection, use highway=traffic_lights
There is no further tagging needed. There is nothing special about this type of crossing - they might not be common in the US (I don't know), but there are plenty of them in use in Europe since decades.

Fixed several 'maxpeed' tags - could you check if I got them all?

Hi,
you added the tag "maxpeed:tilting" on a bunch of tracks. Could you edit them and add the missing 's'?

Cheers, Jan

':' versus '_' - there is no functional difference between the two. Usually, ':' is used for subkeys, e.g. a key that further describes the main key, e.g. 'capacity' and the more specific 'capacity:disabled'. The underscore is more used like a replacement for a space as in "internet_access". In your case I would use a colon.

Alright, I haven't seen this before.
I see one potential problem with the tagging: A barrier=* implies an access restriction, by default access=no. So, if anybody by mistake adds a common node with any highway, routing engines might think traffic is blocked.
I don't think we have a proper tagging for such a symbolic barrier yet - what about using a fully new tag like eruv=*, and subkeys like eruv:type for details? I don't know if similar concepts exist in other religions, maybe one wants to add a religion or denomination tag to make things clear.

Hi,
could you explain the meaning of 'eruv' on this way?
way/513968801

Cheers, Jan

Hi,
you added the tag "Wifi_Etecsa = Wifi_Etecsa" on several nodes - this is not a common tag, could you explain its meaning? If it is the operator of the Wifi, consider the key internet_access:operator

Cheers, Jan

Hi,
could you please check the Russian tags on this object? All objects have to use the tags described in the wiki, otherwise this information can not be understood by any software.

деятельность = отдых
деятельность_1 = пансионат
озеро = иссык-куль
страна = киргизия

Cheers, Jan

Hi,
what do you mean using the prefix "will:" on these buildings? The usual prefixes include planned:, proposed: and "construction", see
osm.wiki/Lifecycle_prefix

Cheers, Jan

Hallo,
du hast hier Öffnungszeiten eingetragen - könntest du sie noch ändern, so dass sie nach dem gängigen Schema getagged sind? So lassen sie sich dann auch automatisch auswerten und in diversen Tools anzeigen:
osm.wiki/DE:Key:opening hours

Wenn du unsicher bist, hier gibt es ein Test-Tool: http://openingh.openstreetmap.de/evaluation_tool/

Grüße, Jan

Kein Problem:
http://overpass-turbo.eu/s/qWB

Hi,
welcome to OSM. All objects in OSM need to have a tag that describes what they are. Just putting a human readable description on a node won't do the job. The wiki shows how these tags should look like, e.g. here: landuse=basin

Jan

Hallo,
du hast hier mehrfach 'raised:building' geschrieben - meinst du 'razed'?
Jan