As with the Changeset comment function which i like a lot this must be a lot more improved to actually be able to review changes. We need

• A better Changeset viewer like this: http://nrenner.github.io/achavi/
• A better way to track changesets in a certain area I use an RSS feed by http://simon04.dev.openstreetmap.org/whodidit/scripts/rss.php?bbox= This must be integrated with OSM itself and be usable without an RSS feed e.g. people have 1-many watched areas in the user config and can have a look at changes of the e.g. last 30 days in that area.
• Telling people to COMMENT on their changeset. 80% of the changesets in my area have an empty or non descriptive changeset comment. So its useless to review as i have no clue what the intention of the mapper was.
• As the nomenclatur of OSM changesets is not the one of a VCS in software development as its not atomic, not self contained there is no way of peer review in the sense of e.g. github. So we need some way to get more people to comment on changes and by thus improving the quality of changes people make.

Its a long way to go but OSM has already come far.

Alles andere ist auch Wunschdenken. Egal was in der DIN steht viele Menschen sind dran gewöhnt kein Lehrzeichen dazwischen zu machen. Und das vermutlich auch noch ein paar Jahrzehnte bis Jahrhunderte so bleiben. D.h. es wird beliebige Schreibweisen geben und damit muss die suche klarkommen.

Ich vermute das Nominatim da so seine schwierigkeiten haben wird. Für “Fuzzy” matches ist das dingen einfach nicht gebaut. Das funtioniert da ja schon nicht bei “-“ vs “ “ in den Straßennamen oder “ö” vs. “oe” - alles schwierig.

Flo

Leider ist der Housenumbervalidator nicht so populär wie der Adresslayer der Geofabrik. Ich habe die Geofabriker schonmal angeschrieben ob man das nicht integrieren könne. Hatte da auch noch mehr ideen für den Adresslayer um fehler zu finden.

Die Housenumbervalidatorfehler sind aber nicht fatal. Eine vernünftige applikation sollte damit umgehen können. Ich habe immer mal wieder 2-3 Bugs wo Gebäudeteile alle die Adresse Erben. Dann landet man vor dem Gebäude egal welche Adresse man aussucht. So what.

Bei keepright gibt es jede Menge Kategorien die ebenfalls irrelevant sind (in meinen Augen) z.b. wenn die URL auf einem objekt die Keywords nicht enthält. Etc. Nur etwa 10% der Kategorien würde ich als wirklich definitiv fixenswert im Sinne der Datenkonsistenz halten.

Schöner ist natürlich wenn das wirklich sauber ist. Aber nicht um jeden Preis. Leider führt hier der Übereifer so wie bei den Wochenaufgaben auch mal zu kontraproduktivem Verhalten von Mappern.

I’d vote for using the MapOSMatic stack for producing the FieldPaper PDFs. Lots of stuff has been solved and its easy to set up. Only the rectifying markers + QRCode needs to be put in there but then you’ll get a 99% Vector PDF which is smaller and scalable to any paper size you’ll decide to print on.

It’s so funny: I have been visiting the Netherlands very regularly and since 2009 i am also mapping where i was. From the AND import the landuse is completely broken. Overlapping landuses. Single trees als landuse=forest. footways as service roads etc. The AND Data should not have been imported in the first place. We had imports in Germany too for example the postcode areas. These were offered as osm.xml files so MAPPERS visually validated the data before it ended in the OSM Database. Its a little slower than an automated import but you gain people who identify with the data and fix it where knowingly broken.

Then in 2009/10/11 i added addresses in NL - Not a lot but what i could do in 2 weeks. Those addresses are all gone now after the Adress import. Not that i think that my contribution was better or more complete than the Addressimport - But think about the psychological point - By deleting user contributed data, replacing it with imports you tell mappers that their contribution is worthless. So you destroy your community you started to gain.

Automated Imports might bring you more complete data by the cost of destroying your community.

“OSM was built around the notion of mappers collecting or curating data and then adding it to our central repository, iteratively improving the quality and completeness over time.”

It hasnt been like this everywhere. This might be the altruistic vision of OSM.

Just look at the Netherlands. There were huge imports of AND Data in 2008 and later with Address data just lately. Still the quality is still poor. Mistakes have been made while importing and due to the visually complete data the NL community has failed to attract a lot of mappers. So IMHO NL is a negative example of imports and fast working.

Yes - there a lot of data consumers who want full datasets and they want it now - I’d be one of them. If we had full address data for Germany that would make my life a lot easier.

Still - I am very patient. I am very confident that one day OSM will have all the data i’d need, until then i am working every day to add stuff i need. Addresses, streets, footways etc.

Back when i started with OSM everyone said - “You’ll never complete the street network”. I responded - the more attractive OSM gets the more Work will be done. Its the same now. The more people/companys start using OSM the more data will get added, the more detailed the data will get, the more addresses will be surveyed or imported. There is nothing wrong with this. Its just the reason people contribute to OSM changes. In the early days it was a purely altruistic way of “i have mapped my neighbourhood”. Now its - “damn - that address is missing - hey OSM your dataset is broken”.

Still - OSM is the best Geo-Dataset in the world and it’ll stay that way. There cant be any economical competition when you calculate your man-hours with nil.

Be optimistic and patient.

Flo

I certainly disagree with this:

“do not: use notes as your own notepad while mapping, unless you expect someone else to fix it.”

As long as those notes are verbose enough for others to be useful to add or correct data its nothing wrong with using notes for missing/wrong informations in the map.

Verbosity is a key issue. Be shure to build enough context to be useful for others.

Completely missing is the context when closing a note. Closing a note without a message is a complete nogo. I am always tempted to reopen the note with no message when somebody closes the note with no message. When you fixed something - write it in the close message.

Flo

I stopped taking Mapillary images from inside the car. Reflections on the front windscreen make images of less quality. And on most car/mobile phone combinations you’ll have some bonnet on the lower part of the screen.

This is my solution with a little wood sawing and 2 screws:

Car Roofmount

Aber wie immer - Alles benutzen mit Hirn. Es gibt Hausnummern die in der ALK drinstehen aber nicht in Benutzung sind - Da haben sich offensichtlich Hausbesitzer mal 5-10 Hausnummern (Buchstaben) auf Vorrat zuteilen lassen. Dazu kommt das es Hausnummern gibt die nicht in der ALK Stehen. “Mein Sohn hat angebaut - Da kleben wir jetzt mal einfach die 10a dran”.

Ich habe teilweise 5% Abweichungen von anderen Datenbeständen.

The Editor gets a little strange when you have e.g. Restaurants which have Tu-Th 18:00 to 2:00 and Fr-Sa 18:00 to 5:00 Su/Mo Closed.

Results look strange IMHO whenever you cross the 24h/0h boundary.

Flo

Numbers:

The String addr:countryDE 32768 times in a file is 950272 bytes. Compressed with bzip its 280bytes - Thats a compression ratio of 3393:1.

Using your number of 4826424 tags at 29 bytes with the above compression ratio results in 41251 bytes.

So ·~40KByte of the planet are for addr:country=de - I dont think its worth the discussion or the hassle for Data consumers.

I have added 30000+ Adresses to OSM in the past 7 Years, and i am a heavy consumer of that Data too. There is no such thing as “duplicate tags”. Self contained addresses are a wonderful thing. The associatedStreet relation has proven that its too complex for people to handle, and to complex for people to consume. There are tons of tools out there which refuse to work with non self contained addresses where part of the tags are missing, or where the exact address resolution need complex spatial request to a full planet database.

All these in your eyes “duplicate tags” can be compressed away with very little cpu power so i dont see any point in making it complex for people and consumers for saving a few bits.

Hi, in der tat sollten wir mal wieder was machen. Am besten auf der osm-owl liste:

http://gt.owl.de/cgi-bin/mailman/listinfo/osm

Flo

Aeh - Sorry - ist natuerlich quatsch - Köln Dellbrück ist nicht in Delbrück und damit nicht in OWL

Wird nicht einer alleine sein. Trag dich mal auf der osm-owl liste ein da werden die wohl alle abhaengen.

http://gt.owl.de/mailman/listinfo/osm

Ist IMHO kein konsenz. Und wenn es nur dient zu zeigen was bereits erfasst ist.

Ich möchte der neuen Lizenz eigentlich auch nicht zustimmen aber der Schaden den ich dadurch anrichte d.h. das Loch das ich reisse wird schon beträchtlich sein. Schlussendlich habe ich OSM gemacht um eine _FREIE_ Karte zu bekommen. Die Odbl ist fuer mich das Gegenteil. Einschraenkungen wohin das Auge blickt und eine komplexität die ich niemandem zumuten möchte.

Ich bin ganz entschieden für PD weil es eben die Freieste der Lösungen ist. Und wer das Thema Lob andiskutiert ... Die Nennung wird ganz selbstverständlich kommen denn alle ernsthaften Nutzer der OSM Daten werden um ein gutes Verhältniss bemüht sein. Und am besten fände ich so etwas wie den Debian Social Contract - der zwar keine Rechtsbindung hat - aber eine Moralische bindung.

Ich loesche das nur auf objekte die ich auch tatsaechlich aendere. Das hat den vorteil das nicht nur fuer das entfernen der created_by ein change geschrieben wird - Das erzeugt auch datenmuell in den changes die die ganzen downstream mirror verarbeiten muessen.

In my eyes you have qualified for "Best of OSM" instantly ;)

I think i have seen some landuse=meadow in the back - ah - and barrier=fence on the way too.