Hi,
this import contains tags which don't seem to belong to OSM, like OBJECTID and Shape_Area. Could you have a look and remove these?

Jan

Hallo,
du benutzt hier das Tag "socket:type:output" - das gibt es so nicht. Für "type" müsste der jeweilige Typ des Anschlusses eingesetzt werden.

Gruß, Jan

Hi Michel,
you used the key "vitesse" to tag the allowed speed on these radars - the correct tag is "maxspeed". Please note that all tags have to be used as documented in the wiki, otherwise the data can not be understood by any software.

Another point: The "name" tag is for the actual name of an object, not for a description or a reference number. E.g. "RADAR A1, 6.4 Km (PK 6+400)" doesn't seem to be a name, but rather an (internal?) reference.

Jan

Hi,
it looks like something went wrong here, there are 16 nodes with these tags:

----addr:housenumber=DELETE
----description=DELETE
----null=DELETE
----opening_hours=DELETE
----phone=DELETE
----website=DELETE

Could you have a look?
Jan

Hi,
it looks like something went wrong here - you've added 7 multipolygon relations that don't have any valid tags, just imported tags which typically shouldn't appear in OSM.
And there are overlapping landuses, e.g. a forest overlapping with several scrub areas which can't be right.

Could you have a look and fix that?

Jan

Hi,
could you check this node?
node/5328345520
It looks like you forgot to exchange the tags with proper ones.

Jan

Hi,
you added the tag 'ja-Latn' to several objects - the correct tag would be "name:ja-Latn". I just fixed this in the cases I found.

Cheers, Jan

Hi,
you used the tags "opz inscription" and "opz monument" - what is the meaning of the "opz " in front of the usual key?

Cheers, Jan

Hi,
could you check this way?
It has only strange tags:
way/551736946

Cheers, Jan

Hi,
please pay a bit of attention to the correct spelling of tags - everything with a spelling mistake can not be used by any software.
E.g.
addr:number -> addr:housenumber
building:contruction woold fram -> building:construction = wood_frame
buildings:level -> building:levels
buildings:level:underground -> building:levels:underground
and others.

Jan

Hi,
I found a spelling mistake in some tags:
It should be "addr:conscriptionnumber" not "addr:consriptionnummer". I fixed most of these, but there might be some I missed.

Cheers, Jan

We do have "preproposed", "proposed", "planned", "construction" as possible values for not-yet-existing ways. 'purposed' is not one of them.

Could well be.
I found the tag
"Sudecka = Beskidzka"
I assumed this was a simple error while copy-and-pasting. But it could be "name = Sudecka" as well (which I think makes more sense)

I found it in the list of new tags in the OSM database:
http://osm.mueschelsoft.de/taginfo/newkeys.htm

Hi,
could you check this way? It's missing some proper tags.
way/551439874
Cheers, Jan

Hi,
you added some tags like "leisure_7" to this park - unfortunately this information doesn't help. Most software only interprets the 'leisure' tag, but none of those with a number like _7. You can add this amenities on individual nodes at their actual place.

Cheers, Jan

Essentially all subtags to destination are only proposals, none of them has been voted on. destination:lang:XX is being used many times (> 1000) which suggests it should not be changed. The same is true for the 10,000 objects with a destination with ':to' subkey.

I don't like the idea to have :lang only for 'destination', but not for destination:street. This sounds incoherent and strange to me.

Please join the discussion on the Talk page to get all the opinions together!

Hi,
welcome to OSM!
Please make sure you add tags like "building=yes" only to the outline of the building, not to each individual node.

Jan

Hi,
you added some "destination:street:en" here - the tag should be "destination:street:lang:en" to avoid ambiguities. osm.wiki/Talk:Proposed_features/Destination_details#destination:street_multilingual

Could you change that?

Hi,
could you check this way, it looks like it was uploaded by mistake:
way/551037479

Cheers, Jan

Hallo,
dem "access:conditional" hier fehlt noch ein Wert - ich vermute es muss heißen
access:conditional = yes @ 08:00-20:00

Gruß, Jan