OpenStreetMap logo OpenStreetMap

Changeset When Comment
122853522 over 3 years ago

Thanks for the reply!

I think several of these issues can be fixed easily.

- we do have a complete set of tags for toilets
- "addr:quarter" or "addr:district" should be adequate instead of quarteirao (based on Google Translate)

I don't know what the other tags mean, translation is not really helpful.

122853522 over 3 years ago

This seems to be an import of some kind and I found several issues:

- house numbers are duplicated, they were already in OSM before

- it uses many non-standard tags:

addr:quarteirao 29
compartimentos 3
deposicao:rsu txovas
fornecedor:agua FIPAG
localizacao:torneira Exterior
population 8
toilet pour_flush_toilet

- it contains private data. Things like the number of inhabitants of a building should not be in OSM.

Please make sure that you only use tags that are documented in the Wiki and not to disclose any sensitive data about people.

122455585 over 3 years ago

Das richtige Tag für Parkplätze ist
maxstay:conditional = 1 hour @ (08:00-19:00)

122455585 over 3 years ago

Deine beiden Tags hier sind die einzigen in der ganzen Datenbank. Dein Wiki-Link beschreibt "parking:condition:left:time_interval" zur Verwendung an Straßen, aber nicht "parking:time_interval". Das sind völlig verschiedene Dinge.

parking:lane:* und amenity=parking können nicht gemischt werden.

122811972 over 3 years ago

Hi
please check this node, I guess something went wrong with the name tag:
node/9844633057

122835042 over 3 years ago

Hi,
you added these objects with strange tags like
ZONECODE = CO
ZZC = Commercial
This doesn't seem to fit to OSM - could you check and fix this?

122466504 over 3 years ago

Hi,
you added several objects with a strange tag "Museu = Parragem" - could you check and fix this?

122455585 over 3 years ago

Hallo,
'parking:time_interval' gibt es sonst nirgends. Was möchtest du damit sagen? Dass nur in dieser Zeit dort geparkt werden darf? Das wäre "opening_hours".

122789313 over 3 years ago

Hi,
there is no need to add a 'disused' prefix to tags that have a date in the key like
disused:amenity:--2016

The date is sufficient to tag that the amenity is not used any more. So, either
amenity:--2016
disused:amenity
is perfectly fine.

122854927 over 3 years ago

Please don't try to fix any issues with nodes and ways here. This is an undocumented import with many mistakes that most likely needs to be reverted in full.

122852852 over 3 years ago

This looks like an undiscussed import.
What is the source of all the data?
It seems the sizes of all the "buildings" is quite wrong, they appear to be much smaller on aerial images.
There are many foreign tags that don't look like they belong to OSM, and you ignored thousands of warnings from the editor when uploading the data.

I suggest to revert the whole import for now, so that you can start a proper import as described in our guidelines from scratch.

osm.wiki/Import/Guidelines

122258729 over 3 years ago

Hi,
is "text:arrow = white" a mistake? Shouldn't is be 'colour:arrow'?

122294957 over 3 years ago

Hi,
please explain why you deleted a building and replaced it by 30000 badly aligned nodes and ways without any meaningful tags?

If you plan to import a detailed map of a building, please follow the OSM import guidelines!
osm.wiki/Import/Guidelines

As is the data is not useful for OSM, and IMHO should be reverted to the original state.
(individual toilet seats with > 100 nodes are not useful in OSM!)

122045683 over 3 years ago

Hi,
welcome to OSM!
I found some strange tags on the objects you added like these:
historic = first_petroglyph_of_this_trail.
historic trail = *
These might be good descriptions of the objects, but are not usable like this in OSM.

In OSM we have to use a well-defined set of tags to allow all the software tools to understand the data and e.g. show it on maps.
Please make sure that you only use tags that are documented in the Wiki or are available as presets in your editor.

Jan

122136029 over 3 years ago

Hi
could you check this node? It got a 'uic-name' and a 'uic_name' tag.
node/2483323431

122571397 over 3 years ago

Ja, das ist kompliziert :)
Eigentlich kannst du 'bicycle' sogar weglassen - "oneway" bezieht sich ja an sich nur auf Fahrzeuge, nicht auf Fußgänger.

Ich habe hier versucht die Reihenfolge allgemeingültig zusammenzufassen:
osm.wiki/User:Mueschel/OrderOfKeyParts

Hier haben wir:
[Key][Side][Vehicle][Subkey]

sidewalk ist der Key
left ist die Seite
bicycle ist das Fahrzeug
oneway ist ein Subkey

"oneway:bicycle" passt auch wieder, weil "oneway" hier Key ist.

121995572 over 3 years ago

Could you check this tree? It got two strange tags:
node/9795188772

122585086 over 3 years ago

Hi,
welcome to OSM!
I found a couple of unusual tags on roads you edited, for example:
eclairage = yes
onas = yes

These are not used by anybody else.
In OSM we have to use a well-defined set of tags to allow all the software tools to understand the data and e.g. show it on maps.
Please use only keys that are documented in the Wiki or are available as presets in your editor.
Thanks!

122122892 over 3 years ago

Strange... that's not what I remembered, but it has been there for a long time.
So: Ignore what I said. Sorry!

One thing that maybe should be done: Change the definition for Key:toll so that it is allowed on toll_booth nodes as well. Currently it's only for ways according to the Wiki.

122122892 over 3 years ago

'disabled', like 'delivery', is not a type of transportation, so this rule doesn't apply.
It relates only to types of vehicles, like hgv, bus, bicycle...

Note that we don't use
motor_vehicle:disabled = yes, but motor_vehicle = disabled

So, this would be fine with me:
toll:conditional = no @ disabled
but
toll:disabled = no
doesn't fit to current standards.