Hi,
you used the tag "adminl_name" here - is this a mistake and should be "admin_name" or more common "official_name"?

Hi,
could you check these ways?
Tags like these look like a mistake:
normalized_volume=0.80101144
priority =0.93589884

Jan

Hi, could you check this way? way/550839519
"highway = purposed" doesn't seem to make sense.

Cheers, Jan

Hi Felipium,
welcome to OSM!
You used some tags like "Sede = Junta Vecinal" in your edits.
This might be a good description of the object, but is not usable in OSM - no computer software can understand it. Only tags that are described in the wiki or are available in the menues in the editor should be used.

Would you mind checking these tags and change them to documented ones? Let us (e.g. on the forums) know if you need help!

Hi,
you used the tag "suface" on 96 ways - could you correct its spelling "surface"?

Cheers, Jan

Hi Pablo,
welcome to OSM!
You used some tags like "lugar de fistas" in your edits.
This might be a good description of the object, but is not usable in OSM - no software can understand it. Only tags that are described in the wiki or are available in the menues in the editor should be used.

Would you mind checking these tags and change them to documented ones? Let us (e.g. on the forums) know if you need help!
Jan

Hi Andreia,
welcome to OSM!
You used some tags like "srviços", "contactos" in your edits.
This might be a good description of the object, but is not usable in OSM - no software can understand it. Only tags that are described in the wiki or are available in the menues in the editor should be used. Some of these tags in your edits might be 'phone' or 'description'.
Would you mind adapting these? Let us (e.g. on the forums) know if you need help!
Jan

Hi,
something went wrong here. There are 27 ways with just tags like the ones below, but no actual highway key or similar. Could you have a look and check that?

IdentifierKey=MDP_8885240585674293249
Name=McIntyre Ln
PlaceType=Street
PrimitiveId=8885240791832723457

Jan

ruins: is used more often than ruined: and nonexistent: is not used anywhere else.

Why not add razed: to the lifecycle prefixes? This should not be a problem, the page is just a plain list of used tags, not proposing any. Used already >>1000 times and would be a good fit, also because xzy=razed is also quite common.

I don't think we need new tags.

Hi,
welcome to OSM. Please spend some time to read about how tagging works, e.g. in the wiki or http://learnosm.org .

I don't know how you managed to create tags like these, but there should be just one word as a key and one as a value, but not many in a row:
boundary=national_park=leisure=pitch
landuse=grass=leisure=playground
leisure=garden=natural=heath
leisure=golf_course=landuse=meadow
leisure=nature_reserve=landuse=recreation_ground
leisure=park=natural=scrub

Jan

Hi,
well, the Wiki specifically asks to use "destination:lang:en", to make clear it is a language.
As example: destination:street:to - is this a street further away (like in destination:ref:to), or is it a Tongan street name?

For me, this points to that this syntax should also be used for other destination-subkeys.
There are e.g. destination:to:lang:en and your destination:street:lang:en.
osm.wiki/Proposed_features/Destination_details#destination:lang:.3Clanguage_code.3E
I see that you added a few lines to this page in October promoting destination:street:en, but this was never discussed on the Talk page of this proposal. A local mailing list might not be the best place to discuss such issues with influence on global tagging. E.g. there are some destination:street:lang:en also in Asia. These are few, mainly because street names are not commonly used as destinations in Western Europe.

Concluding: Yes, I would mind if you change it, because it wouldn't fit the rest of destination tagging.

1. It was many more, It took me > 1 hour cleaning this up last week.
2. 'Unnamed' is definitely not what should be in a 'name' tag.
3. The Tiger import is more or less the worst example for any import ever done. It just dumped data to OSM without any quality assurance.
4. There is nowhere a recommendation to put highway, building and source tags on nodes which are 'just' members of a way.

Plus the comments I gave on the second discussed changeset.

- Large scale imports like this need to be announced, discussed and documented which doesn't seem to be the case.
- All tags used must be described in the wiki

Hi,
as I wrote in the linked comment, there are several things wrong here:
- Nodes must not have the same tags as the way belong to.
- The objects should not have a source tag - this goes to the changeset.
- There are > 10,000 nodes with just a 'colour' tag.
- There are many buildings overlapping roads.

And, as naoliv wrote, we were not able to verify the license of your data, which means it might have to be removed completly.

I wanted to delete the two tags which shouldn't be there:
LUG11 = 018723
LUG11DESIG = Colmeosa

Essentially, if the way is a closed line, there is no need to have a separate relation. In most cases, the ways are not closed and you need a relation to combine them to form a area. This method avoids overlapping lines where the boundaries of two areas meet.
As it's done now it is fine.

Hi,
these 12 buildings got the tag "mota = 12". Was this a mistake?

Cheers, Jan

Hi,
could you check the name of this building? The tag looks like a mistake:
node/5147604164

Thanks, Jan

Hi,
you used the tags
place:subward and place:ward on these buildings - these are new and not documented.
If it's part of the address, the tags should be addr:subward and addr:ward.

Jan

"razed:" is also quite common: https://taginfo.openstreetmap.org/keys/razed%3Arailway#values

For these long-gone objects it might indeed be better to remove them completly, but others might disagree.

Hi,
these ways are missing a 'highway' tag to describe what they physically are.
The tag "rutenummer" is new and undocumented. I guess it should be 'ref' - the reference number of the way.
Could you have a look and fix this?

Cheers, Jan