mein JOSM Fehler war nach einer Woche gefixt :-)
Danke, Alex

bitte mache einen JOSM bug daraus, damt JOSM gefixt werden kann. JOSM darf bei keinen Daten abstürzen!
Danke, Alex

I do not add it any more. But I see a general conflict with OSM rules "international project".
gnis:ST_alpha == only in US,
is_in:iso_3166_2 == rest of planet,

removed again for this relation, but todo (next days) for others

again: how to calc the area of nodes (like place=ocean, that do not have any border) ?
Who should question the free usage of facts?
I understand that area can be calulated 'easy' for smaller objects. But why download megabytes to get one number?
With this argument we should stop overpass-turbo.eu, because anything can be done using planet.osm file. Sometimes a shortcut to information is usefull. Why not make it more comfortable?

Hi Michael,

please read my points.

1. how to calc area of oceans (node, no borders) ?
2. all segments have to be in same orientation (e.g. clock wise) before calculation, which is not assured.
3. Huge Relations (e.g. russia.osm = 37 MB), that is much to download for get one number.
4. OSM has many questionable data: uniqe-keys (single usage), is_in:* (could be calculated too), etc.
5. www.wikidata.org is free: Creative-Commons-Lizenz CC0 1.0 Universal (CC0 1.0) Public Domain Dedication
==> source could be made wikidata (sorry for this)

please follow the osm guidelines for wikipedia-key!
osm.wiki/Key:wikipedia#Examples
wikipedia="languange:Name" eg. "es:Name".
Thanks alot, Alex

please do not use empty keys, like ""="text".
I fixed 2 buildings from this changeset. thanks, Alexander

Hi Hnatyuk,
please follow the guidelines:
osm.wiki/Key:wikipedia#Examples
wikipedia="lang:Article Title Name" not wikipedia="http..." . this makes it easier to use the date, because 99.99% if wikipedia keys use the style from guidelines, and only some single ones (<10) not. Thanks, Alex

opengeodb will have no updates in future (since 2008). some tags lost their need, e.g. :version :auto_update : sort_name :is_in (covers is:in) ==> cleanup these old tags

opengeodb will have no updates in future (since 2008). some tags lost their need, e.g. :version :auto_update : sort_name :is_in (covers is:in) ==> cleanup these old tags

please follow the guidelines for wikipedia tag,
osm.wiki/Key:wikipedia#Examples
wikipedia="lang:Article Title Name" , this simplifies usage of osm data.
thanks, Alexander

Hi naoliv, what is the advantage of the "extensions" tag? disadvantage is: it contains xml-code, that is blowing up the data and breaking some tools to analyze the data. there is no other node on earth using it. thanks, Alexander

Yes, please fix these corrupted tags. I marked them (12 nodes) by "fixme".
Thanks alot, Alexander

what means key "I=1" (unknown key, not used anywhere else on the plant).
Could you please fix this?

please follow the wiki-guidelines:
osm.wiki/Key:wikipedia#Examples
wikipedia="lang:Article Title Name" .
This helps processing/using the data. Thanks, Alex

please follow the wiki-guidelines:
osm.wiki/Key:wikipedia#Examples
wikipedia="lang:Article Title Name" .
This helps processing the data.

please follow the guidelines for wikipedia-key, see osm.wiki/Key:wikipedia#Examples
==> no full link, only "fr:Title of Aricle"
This makes it easier to use (same style for all wikipedia-tags). Thanks

please use only valid tags, not "source="

please do not use empty keys, like osm.org/way/442768353