Welcome and much fun! ;)

Wenn du dir einmal die Zeit genommen hast, die Fehlermeldungen von JOSM genau anzuschauen, kannst du doch ein wenig Nutzen daraus ziehen.
Beispielsweise doppelte Knoten und selbstüberschneidende Wege sind immer falsch.
Leider spuckt JOSM auch unsinnige “Fehler”meldungen aus - die kann man aber in den Validator-Einstellungen deaktivieren.

Welcome to OSM.
I wish you happy, addictive mapping and some nice co-mappers around. :) Using this map you can have a look who works in your region.

PS: Besonders lustig sind Grenzen, die mit anderen Objekten verknüpft sind

Since a comment I wrote regarding HOT got a little lengthy I posted it as a blog entry of mine: @malenki/diary/20179

@ Achterin: Ich habe früher™ selbst gern landuses an Straßen geklebt. Nun gibt es auch bei mir vernünftige Luftbilder und ich könnte mich selbst in den Allerwertesten beißen. Die aneinander geklebten Objekte wieder aufzudröseln macht einiges an Arbeit. -.-

Probleme, die ich öfter (gesehen) habe:
* Lücke in der Straße - weil der Mapper wohl nicht gesehen hat, dass der Straße mit zwei angeklebten landuses ein Stück fehlt
* Wenn man die Lage eines Objektes korrigiert, wird das andere sinnloserweise ebenfalls geändert. Das ist besonders lustig, wenn die Straßenführung für längere Zeit oder dauerhaft geändert wird.
* Dass das Bearbeiten solcher Konstrukte umständlicher ist, hat nichts mit “sich nicht rantrauen” zu tun, sondern ist einfach eine Tatsache trotz Mittelklick in JOSM. Was machen die Benutzer anderer Editoren? Das Objekt Punkt für Punkt einzeln anfassen? Sehr lästig! Wie können die ein Tag der Straße ändern? * Eine Straße ist kein eindimensionales Objekt mit einer Breite = null. Wenn du Felder an die Straße klebst - zeichnest du die Felder damit bis zur Mitte der Straße oder nur bis an deren Rand?

It seems like you could do with the JOSM-Update-Script. I use it in ~/ so there is no need for superuser-rights.

hth
malenki

Ich hatte schon langer Zeit überlegt, meinen Logger in einen ZipLoc-Beutel zu packen, den auf ein großes Stück Styropor zu kleben und das ganze ins Wasser zu werfen. Hab mich aber nicht getraut. :)

(haven’t read the comments so far, but wrote a reply offline)

@lxbarth/diary/20060

Make it much easier to see who’s mapping in an area

+1

Ideally shut down private messaging to avoid abuse

Bad idea. So far I have some hundreads message read and sent and I cannot remember any one of them to be abusive.
While removing a potential place of abuse you’d kill a well working feature of communication.
All the places you mention like faecebook, googlefoo and linkedin: do they all lack a private messaging feature?

Rename ‘friend’ to ‘follow’

+1

Kill the home location feature including the map on the profile
Replace the useless friend listing and ‘in your area’ listing on your profile with a list of latest edits by who you’re following

I’d prefer lists of:
users mapping in my region
users mapping and /living/.in my region

My 2 cents: Don’t go and push some new foo to the people just because you think it helps communicating - and people first have to invest time to learn to handle the new foo.
I for my part am fine with communicating setup at the moment.
Since I am an OSMapper I prefer mapping over discussing the zillionst (maybe useless) topic. Sure there are things which have to be discussed but if I’d involve in heavy discussions on ever platform I had to stop mapping. This would be a sad thing since there is such a lot to do. (Even the data from my summer holiday made it only partly to OSM so far.)

For Github: Lately I had learned that tickets for osm.org should be filed in GH. iD is originally (afaik) placed there and some more stuff related to osm.org iirc.
One thing I liked OSM for is that there was one central place for bugtracking a lot of stuff. Just go to trac.osm.org, open a new ticket and select the feature you refer to. Now it seems there are several places where you can bugtrack. If Github is so cool (I just file tickets there, too) then would be very nice of the admins/webmasters to create a single point of report at GH for OSM stuff.
I dislike to do search for every project I want to file a bug. The higher the stakes before reporting, the less likely I (and assumedly others) will report. And: hopefully there are some thoughts about a possible failing of the 3rd-party site of GH.

Was meinst du mit
“Uhrzeiten mit Punkt statt Komma”? Uhrzeiten selbst sollten doch einen Doppelpunkt haben und getrennt werden durch Strichpunkte? Afaik haben weder Komma noch Punkt etwas in opening_hours verloren.

Ansonsten: Interessantes Fazit

Looks indeed quite helpful.
One question: if the user opens an object in JOSM isn’t it possible to load the surrounding area also by remote control?

Was auch geht:

• neu malen
• alten Weg durch neuen mit “replace geometry” ersetzen
• (gegebenenfalls nun unverbundene Wege wieder verbinden)

Why are two roads glued together..? (link?)

For the rest: I’d assume Bing Imagery can give enough reason to glue landuse to the highway. In earlier times (of bad imagery) I did this, too, partly - and now I unglue that stuff again.

I agree with you that there are situations where gluing landuses doesn’t make sense. Sometimes I also merge identical landuses which are side by side. But for some of your examples I have arguments against your reasoning:

• boundary on a river
  First it would be interesting where the boundary data comes from. When it is imported it is already a bad idea (imho) to glue it to a river traced from Bing since it is likely that the imported data is more exact. The other prolem is: rivers do change. Are boundaries updated by law the same way as the river wanders year by year?
  The quality of aerial imagery changes. Just yesterday I reworked parts of river Osum which had been mapped by using low resolution imagery and now with hi res has offsets from ~100 to 500 meters.

Thus I unglue the ways when I happen to enhance a river and find it glued to a boundary

• two identical landuses
  can have different owners/operators or different names.
  It is also possible that the tagging of one of them just recently got changed.
  </nitpicking> ;)

PS: to select a way from a bundle of glued ways, in JOSM use middle click and hold the list with ctrl.

Willkommen bei OSM!

Ja, es ist erwünscht, dass alle Wohngebäude eingetragen werden. Du darfst sogar die Nebengebäude abmalen. :)

Was du verbessern könntest wurde bereits erwähnt.

Zum Zeichnen von Gebäuden empfehle ich dir das Plugin buildings_tools. Ein rechtwinkliges Gebäude ist mit zwei Klicks und Ziehen gezeichnet; in den Einstellungen lassen sich automatisch zu verwendende Tags festlegen. Mit “Flächen erstellen” (oder “X”) kannst du aus Gebäuden mit zwei weiteren Klicks (zwei Nodes auf dem Gebäudeweg erzeugen) und einmal ziehen bequem z.B. ein rechtwinkliges Vordach erzeugen.

hth
malenki

Thanks for your comment - your script looks very useful for self-diciplined mappers or a dedicated mapping task. But during my holidays I collect a big variety of things so I cannot say I’d replace $A with $B.

I had taken some pains to test the “Road-Detect”-foo some years ago and was as disappointed as you.

For scanaerial you’d need a WMS which serves good aerial imagery - it is not limited to Bing. Regrettably the ancient lakewalker was hardcoded to use landsat imagery.

Besides I found scanaerial not much of a help when there were waterbodies to trace whose color wasn’t uniform like lakes reflecting the sun at ripples where the wind blows over it or where the color of the water changed with the depth of it.

I look forward to your road tracer and am volunteering in case you need some people for testing.

Happy coding/mapping :)
malenki

There is “replace geometry” in utilsplugin2 with which one can work very conveniently.
Other way to make this edit:
* split the way with the relations on it two times
* unglue the nodes of the segment
* insert the segment with all the relations where you like

If you map a feature as area for which before just a node existed you should not delete the node but use it on the area (with all tags removed).
So other mappers can follow more easily an objects history.

To make such an edit easy use “replace geometry” (which tool is iirc contained in utilsplugin2).

You should map the usual valid maxspeed value. To map more than just one maxspeed=xy you should have a look at conditional restrictions: osm.wiki/Conditional_restrictions