Nakaner has commented on the following diary entries

Post When Comment
New road style for the Default map style - the full version 12 months ago

Hi Mateusz,

I really like your improvements, especially your huge use of service=* on railway tracks.

Best regards


Stammtische und Berlin im Detail almost 1 year ago

Wenn ihr derzeit (d.h. seit ihr im Resonanz seid) durchschnittlich nur auf gut 6 Besucher pro Stammtisch kommt, ist das für die Größe Berlins eigentlich erschreckend wenig. Karlsruhe, das nicht mal ein Zehntel eurer Einwohner hat, hat gefühlt im Schnitt genauso viele Teilnehmer. Liegt das vielleicht daran, dass der Karlsruher Stammtisch eine Abspaltung der örtlichen LUG war? Oder liegt das daran, dass in Berlin die Wege aufgrund der Größe Berlins so weit sind, dass manchen der Weg zum Stammtisch zu weit ist?

Vielleicht schaue ich ja bei eurem nächsten Treffen vorbei.

Mapping turn lanes in OpensStreetMap almost 1 year ago

It is no good idea to use relations for turn lane mapping. Roads are very often touched by newbies. Newbies use iD and/or have no knowledge (iD does not help them to get it) about relations.

I hereby strongly suggest neither to use the plugin you promote nor to use relations for turn lane mapping!

Starting up again about 1 year ago
  • Get offset on Bing maps sorted out.
  • Get plug in to handle .gml files available from land registry (INSPIRE index polygon data.)

Data imports must be discussed! See Import Guidelines.

  • Work out how to get more layers such as electoral boundaries , district council boundaries etc.

OSM may not be the right location for electoral boundaries.

  • Find out about adding photos to the map

New road style for the Default map style - the first version about 1 year ago

I would prefer red junction names.

pnorman wrote:

Is switching from blue motorways necessary? I realize that blue doesn't cleanly fit into a yellow orange red scheme, but it's unfortunate to lose a color which currently doesn't conflict.

There is already a conflict! Motorway blue looks similar to water blue.

I had a client who got rendered OSM maps (the Carto-like style of Maperitive) for printing. He asked me first to change the motorway blue to orange because it looked better.

From car driver point of view, there is less difference between a trunk and a motorway. By default, trunk have no speed limit in Germany (like motorways). The only differences are shorter curve radius and smaller lanes. That's why rendering of motorways and trunks should be similar.

New road style for the Default map style - the first version about 1 year ago

I agree with your decision on rendering trams only at zoom 12+ as a railway fan (and co-developer of OpenRailwayMap). I have had a look on tram lines which go kilometres out of their city, e.g. Gotha–Tabarz.

If you go to change rendering of trams, you should also have a look at rendering of light rails (railway=light_rail). Light rails often run near roads (or between the two carriageways). Especially in Germany, we have multiple cities where light rails serve the job of trams, e.g. Stuttgart or Frankfurt (Frankfurt has two separate systems a partially over- partially underground light rail and a tram network). (trams are pink, light rails green, undergrounds blue, orange/black/brown/yellow/red are heavy railway tracks, tunnels are brighter)

Natural Atlas + OpenStreetMap about 1 year ago

Your Terms of Service state:

Geographic location data (latitude, logitude coordinates) from Natural Atlas cannot be used commercially without explicit written concent from an employee of Natural Atlas. If you're interested in this data, please email *****

From my point of view "cannot be used commercially without explicit written concent" is not compatible to OpenStreetMap data license.

  1. You cannot forbid me to vectorize map data from your map.
  2. If your users place the markers based on an OpenStreetMap-based map, these positions are covered by the share-alike of Open Database License.
Häuser zerschneiden… about 1 year ago

zarl schrieb:

Lustiger finde ich diesen Kreisel ein paar Meter weiter in der Krummen Strasse auf einem Parkhaus, der anscheinend von einem Bot erstellt wurde. Wie kontaktiert man den denn?

Der User ist kein Bot, der heißt bloß so. :-) Außerdem sollte jeder Bot auf PNs und Changeset-Kommentare reagieren oder wenigstens auf seiner Profilseite den Account seines "Kommandanten" angeben, den man dann anschreien kann.

Stirbt Talk-de? over 1 year ago

@derFred: Ja, da hast du Recht. Ich überlege gerade bloß, ob ich das tun soll und mal wieder "in ein Wespennest stechen" [1] soll.

[1] ein altgedienter OSM-Aktiver hat das kürzlich zu mir in einem anderen Zusammenhang gesagt. :-)

Trying Overpass API over 1 year ago

The combination of osmconvert and osmfilter (see OSM Wiki) might be a alternative at some use cases, especially if you need data of larger regions (counties, countries, …). You can download the raw data which is the input for osmfilter and osmconvert at I suggest PBF format.

Addresses Revisited over 1 year ago

I think we have more than "1/3 to 1/2" of all addresses in Germany mapped yet. There a lots of buildings without a house number (even in the official cadastre). These adjacent building ("Nebengebäude") like garages or barns often are located on the same parcel and that's why they do not have an own housenumber.

It's time to import TIGER address ranges into OSM over 1 year ago

I fully agree lyx.

America still suffers from an old, bad import called TIGER which has not been fixed yet. Importing the next TIGER data set would be as effective as spraying Roundup on every American mapper (if mappers were plants).

OSM is not a data storage center for public GIS data. If someone needs addresses for the whole US, he/she should download the TIGER address data and add it to his PostGIS database. Because TIGER is public domain, this no licensing problem.

From my low level comparison with Google data in a rural town, addresses were off by 10-20 feet max. More rural areas increased the uncertainty level, but it is significantly better than literally nothing.

I believe that Google uses TIGER addresses in large part of the U.S. They might have added a random error on each address coordinate to be able to prove copyright infringement.

As I wrote at other blog posts: People map if they miss anything. If they miss no data, they do not map, i.e. nobody misses data in rural areas. I think that Frederik's classification of the U.S. OSM community is not as bad as the answer at the Talk mailing list indicate. (There are some people who neither fit in category A nor in category B)

(a) A project for hackers and couch potatoes who trawl their county web pages and other sources to look for stuff they could "upload" to OSM (because it's such a big country and nobody could possibly, yadda yadda yadda)

(b) A project for people who roll up their sleeves, travel to places of humanitarian crises, and help those in need by creating maps where the government hasn't done their job well.

(Actually) fixing the Peoria GIS import over 1 year ago

If an import was a bad import like the one you describe above, it should be reverted, not repaired. If people need really a map in this area they either will reimport the data in better way (simplified geometries, better tagging) or they will map the area by on the ground survey. If there are no mappers in this town, nobody needs the data.

From my point of view, OSM is not the right place for old data. Either import up-to-date data or map it on your own! I would delete the whole data garbage.

Stirbt Talk-de? over 1 year ago

Du hast das alles falsch verstanden.

Der Stadtplandienst mit neuer Technik und OpenStreetMap ist online over 1 year ago

Endlich mal ein städtischer Stadtplan, der OSM nutzt UND einen mir noch unbekannten Kartenstil verwendet! Besonders auffällig ist, dass euer OSM-Layer keinen Hausnummern rendert und stattdessen die Namen der POIs in den Häuser (d.h. Ladengeschäfte usw.) bevorzugt.

Einen kleinen Kritikpunkt habe ich aber noch. Wenn ich ein die topographische Karte anzeige, wird als Quelle immer noch OSM unten rechts genannt. Das ist etwas unschön.

Rückblick auf die FOSSGIS 2015 in Münster und Ausblick auf die Zukunft der FOSSGIS over 1 year ago

@escada: fixed. It looked like a copy-paste error

Rückblick auf die FOSSGIS 2015 in Münster und Ausblick auf die Zukunft der FOSSGIS over 1 year ago

@lxbarth: Ich glaube, dass eine deutsche SotM 2016 eher in Bonn als in Berlin stattfindet.

Öffentlich... over 1 year ago

Suchst du das Lüneburger Mappertreffen, das Mappertreffen in Lüchow und die Lüneburger Mailingliste?

Die meiste Kommunikationsaktivität läuft in der deutschen Community über das Forum (Login mit OSM-Account)

Gebäudemapping in Neubaugebieten mit GPS und ohne Luftbilder over 1 year ago

SammysHP schrieb:

Mein Problem seitdem war, dass ich VisualSFM nicht unter Linux zum Laufen bekommen habe. Da scheint sich in den letzten Monaten aber was getan zu haben, werde ich nochmal probieren.

Ich habe (auf Arch Linux) VisualSfM vom Juli 2014 verwendet und selbst kompiliert. Es ist zwar etwas aufwendig (das AUR-Paket kompiliert die Sourcen nicht, sondern lädt sich die Binaries, weshalb ich dann einfach selbst alles von Hand kompiliert habe), aber es geht. Dummerweise habe ich mir damals keine Anleitung geschrieben.

Brauchbar ist VisualSfM aber erst, wenn du die Hardwarebeschleunigung (GPU) nutzen kannst, sonst braucht SIFT (die Featuresuche in den Bildern) mindestens dreimal solange.

Flächen/Volumenkörper braucht man IMHO keine berechnen und Meshlab mag ich nicht, weil es, anders als CloudCompare, keine GPU nutzt (CloudCompare kommt auch noch mit 6 Mio. Punkten klar).

Relato do Encontro OSM Brasília - Janeiro/2015 over 1 year ago

Reading this diary entry via Google Translator, the addressing scheme of Santo Antônio do Descoberto seems to have similarities to Mannheim addressing scheme. In the town center of Mannheim, Germany buildings are assigned to square blocks (Quadrate) whose name consisits out of a letter and a number. See the English description at tourist information website of Mannheim.

Buildings/Address nodes are tagged

  • addr:housenumber=*
  • addr:place=[square name, e.g. B5]
  • addr:city=Mannheim, addr:postcode=*, …
  • addr:street=[square name, e.g. B5] It is only used because addr:place was invented in 2012 or 2013 when these addresses already had been mapped. Nominatim supports addr:place and that's why addr:street=* should not be used anymore for street-less housenumbers.

The squares are mapped as simple closed ways and tagged

  • area=yes
  • name=B5
  • place=neighbourhood

I suggest not to use multipolygons which refer to the street segments because it is fragile and breaks easily.