In my biased opinion, OSM2World deserves at least a mention, too. ;)

See: http://maps.osm2world.org/?zoom=18&lat=53.62456&lon=11.41839

No WebGL interactivity and animations (yet), but textures, building levels and a few other features.

You will occasionally get multipolygons even for amenities, shops and the like. Some examples (found via overpass turbo):

• a parking ground around a McDonald’s
• an unusually shaped church
• a mall enclosing a garden

Compared with ways and nodes they are of course quite rare – Taginfo says that 0.06% of shops are relations, and about 1% of amenity and leisure features. It’s up to you whether you think including them is worth the effort.

(Sorry for the slow answer, expected to be notified about replies somehow.)

You don’t mention relations. Does your code handle POI mapped as multipolygons, specifically if the tags are on the relation instead of the outer ring?

How about roof:material=grass?

Regarding OSMI: There were some server problems apparently, but it should now begin to work again according to a Forum post by Frederik (in German).

Höhenlinien werden derzeit nicht direkt in OpenStreetMap eingetragen. OSM-Anwendungen, die so ein Feature anbieten, nehmen die Werte normalerweise aus Quellen wie SRTM oder OpenDEM.

In OSM gibt es zumindest den Schlüssel ele, mit dem man einzelnen Punkten eine Höhe spendieren kann. Leider herrscht dort ein bisschen Chaos, was das Messsystem der Werte angeht. Und die Werte werden – soweit ich weiß – von bisher existierenden Anwendungen auch nur zur Beschriftung von Berggipfeln o.ä. eingesetzt.

Go to osm.org/traces/mine which is a list of traces you have uploaded. Click at the file name of a trace. At the bottom of the overview page for that trace, there is an edit button. Click it. You will now be able to edit the description, visibility and tags of the trace. Do so, then click the save button below the text fields.

@Chaos99: vVvA has already contributed and tagged several nodes and ways, so I’m going to assume that this question is indeed about adding tags to traces, not about adding tags to map elements.

I think what you describe in your post is indeed something that should be implemented and would be very helpful for OSM.

Maybe I can help. I’m actually using a bot to extract template data from the wiki already. Right now I’m doing this for the software templates. The software catalogues have been kept up to date using this automated process for years.

Rewriting this as a more general framework for template extraction (preferably in a programming language that is more popular among OSM developers) has been on my todo-list for quite a while - there are several unrelated ongoing projects I would need this for. But once that tool exists, it could be easily used to expose the data from key/tag description sites as JSON, too.

Like other commenters, I disagree with the idea to delete accounts without map edits. For one thing, it is known that some people only start mapping months after they have registered their account. Furthermore, OSM accounts are needed for other services than mapping: Posting in the forum and on help, uploading gps traces, or even just storing your preferences for osm.org. Thus someone who is not a mapper might still be actively using their account - e.g. a developer using OSM who participates in forum discussions.

If the problem is that “find nearby users” is too cluttered with inactive accounts (and I actually agree with that), then the solution is to filter the accounts showing up there, not to delete them entirely.

In communication, reporting the number of people who have actually mapped something, rather than the number of registered users, would indeed be preferable. But that would be possible even today.

Here in Passau, Germany, we mostly just use the wiki write down links and topics from our meetings: Passau/Mappertreffen (Google translate), though we have a landing page with the usual template, current events (if any) and embedded slippy map, too.

These meetings are also our primary means of coordination, along with the occasional email on our local mailing list. Passau is quite small and we usually get just 3-6 visitors.

Years ago, there was an attempt to establish “mapping status” tables on the wiki. While it seems to have been adopted by a few places quite well, it doesn’t really work for us and is unfortunately barely maintained now. What did work, though, was an automated comparison with an official list of street names that helped bring down the number of unmapped streets. I think it mostly worked because it didn’t require any additional effort once it was set up: You just mapped a street and it would disappear from the list.

I agree that a separate account should not be required for small-scale, manual integration of accepted sources. But is there any example where an user was in fact blocked by DWG for making a small(!) edit based on such sources?

The modified elements will become “superseded” the next time they are modified by a human mapper. Until then, it is assumed that they are incomplete (because of the information lost from e.g. deleting tags or removing some of a node’s ways).

@pavithrans: Even if a mapper accepts now, his changes will not automatically come back. This would cause too much problems if parts of the area have been remapped or otherwise modified since the deletions.

@aseerel4c26: You can flag redaction markers in OSMI as “taken care of” by clicking on them, then clicking the small “trash can” icon in the details for the selected entry on the right. (Only works for deleted, rather than modified, elements.)

Wenn es eine 1:1-Beziehung zwischen Gebäude und Adresse gibt, dann sollte der Gebäudeumriss mit der Adresse versehen werden.

In nicht so einfach gelagerten Fällen muss man eine andere Vorgehensweise wählen. Beispielsweise taggen manche Mapper Eingangs-Punkte im Gebäudeumriss (entrance=*) mit Adressen, wenn ein Gebäude mehrere Adressen hat, aber eine 1:1-Beziehung zwischen Eingängen und Adressen gibt.

Ein simpler Router muss eigentlich mit beidem klarkommen, denn dass etwas sowohl als als Fläche als auch als Punkt eingetragen werden kann, ist in OSM ja auch sonst (z.B. shop, amenity, …) üblich.

According to the definition used by several 3D renderers, building:levels counts the number of floors of the building above ground (including the ground floor), but without levels in the roof.

So for building:levels you don’t count underground floors, and you don’t count the attic either. There is building:levels:underground for the former, and roof:levels for the latter.

So, in this drawing …

… you would count P and S for building:levels, K for building:levels:underground, and D for roof:levels.

Unfortunately, I don’t know what “intermediate plant” means.

Und noch ein Kommentar: Wenn du dein Vorhaben mit der eigenen Karte trotzdem noch umsetzen willst, frag doch einfach bei uns im Forum nach Vorschlägen, wie das am einfachsten geht. :)

Ok, sollte jetzt erledigt sein: Ich habe deine Änderungen rückgängig gemacht.

Danke, dass du hier so schnell um Hilfe gebeten hast. So etwas ist nämlich um so leichter, je früher es bemerkt wird (und je weniger an dem Gebiet seither geändert wurde, daher meine Bitte um Zurückhaltung vorhin).

Ja, es geht und ich machs auch gerne. Aber bitte bis dahin erst mal nichts mehr anfassen. Deine Reparaturversuche kommen mir grade beim Rückgängig machen in die Quere…

Ja, das war eine Folge des Lizenzwechsels. Der Weg selber war zwar in Ordnung, aber viele der Knoten stammten anscheinend ursprünglich noch von einem anonymen Benutzer, der wohl nicht mehr erreicht werden konnte.

Hier kannst du sehen, was alles beschädigt wurde:

http://tools.geofabrik.de/osmi/?view=redactionbot&lon=9.39574&lat=52.37999&zoom=15

Im weiteren Umkreis gibt’s leider noch einige Stellen.

Aber immerhin kann ich dich in einer Hinsicht beruhigen: So was kommt wohl nie mehr wieder vor, das war ein einmaliges Ereignis.

Hast du den Menüpunkt “Map Key” oder “Legende” links von der Karte schon entdeckt?