Hedaja has commented on the following diary entries

Post When Comment
spam users ☹ about 15 hours ago

So the example you saw looks correct

spam users ☹ about 15 hours ago

Have a look at power=plant( power=generator ( generator:source= ( generator:type= ( and generator:output= (

Happy Mapping ;)

How we apply map feedback 4 days ago

I think having the contribute action later might be not that bad. If the user reporte a problem and corrected it by himself afterwards Mapbox still knows there was an issue an could control the changes the user made. (Don't know if this is already happening) In my opinion the feedback possibility is quit useful for OSM.

Manpower recruitment services 5 days ago


Umfrageplattform freigegeben 13 days ago

Und nochmal ich: Eine Möglichkeit Email Benachrichtigungen bei einer neuen Umfragen und beim Abschluss einer alten zu bekommen wäre auch klasse.

Aber so schon echt gut und interessant =)

Umfrageplattform freigegeben 13 days ago

Gleich noch was =) Umfragen bei denen man mehrere Antworten wählen kann oder nach Wichtigkeit ordnen (beispielsweise gut für Umfragen wie diese: Möglichkeit zur Übersetzung ;)

Umfrageplattform freigegeben 13 days ago

Schon ein paar mal genutzt, aber jetzt ist mir grad was aufgefallen (liegt daran, dass jetzt so viele Umfragen vorhanden sind) Es wäre schön, wenn bereits beantwortete Umfragen markiert würden.

mfg Hedaja aka Christian

Triển lãm Toyota Camry 2015 tại Thái Lan 23 days ago


Proposed talk at both SOTUM and HOTOSM conferences!! 30 days ago

A possible way to tag:

Aller Anfang about 1 month ago

Hallo hat ja lang gedauert nach der Registierung, aber es ist nie zu spät anzufangen =) Was mir aufgefallen ist, ist dass du die Wege im Wald als highway=footway eingertragen hast.

Hab ich Anfangs auch immer. Eigentlich wird highway=footway jedoch nur für reine ausgeschilderte Fußgängerwege ( genutzt. Ohne die Gegebenheiten vor Ort zu kennen, würde ich eher auf highway=path tippen. Sollte er ausgebaut sein (gepflaster oder so), kann man noch verschiedene Sachen hinzufügen, wie surface/trail_visibility/width um ihn von einem Trampelpfad unterscheiden zu können.

MfG und frohes Mappen Christian aka Hedaja

OsmAnd (Android) und Abbiegespuren about 1 month ago

OsmAnd (Android) und Abbiegespuren about 1 month ago

Using relations fo turn lanes isn't very common. There are around 180.000 uses of turn:lanes and only around 45.000 used segments in turnlanes relations.

OsmAnd (Android) und Abbiegespuren about 1 month ago have a look at "furthermore:" ;)

New to OSM 2 months ago

noticed one thing It would be nice if you would add a short comment for you changesets (when uploading changes). This makes it easier for others to see what you have done.

New to OSM 2 months ago

Hello welcome to OSM =) If you have any problems and questions take a look at these links (

Happy mapping Hedaja

Addressing 3 months ago

If you want to print maps for walking surveys there is a service called FieldPapers ( or WalkingPapers ( If you upload your notes (no matter printed with FieldPapers or WalkingPapers) to you can directly use it georeferenced in JOSM.

Learn-a-tag: leisure=fitness_station 3 months ago

Thanks reminded me that I still haven't mapped my whole travel this summer ;)

Where do you start with replacing shower screen seals? 3 months ago


Voting is bullshit 3 months ago

I can understand both factions. On one side i like the do-ocracy because its is possible to describe new things no one thought of before. But on the other side I'm (like most mappers) are data contributer and data consumer simultaneously. I think if tags only evolve and introduced because they are being used, we are going to get bigger distinctions betwen the different "sub" subjects of OSM (like Railways/highways). A lot of very active mappers tend to specialize on one topic. This means that active mappers might push this topic further without the view for similarities to other things. One example is the way proposed things are tagged: for highway the preferred way to tag is highway=proposed + proposed=type_of_street and for building the slightly more used way of tagging is: proposed:building=type_of_building. Having different ways to tag similar things in different subjects makes it a lot more complicated for cross subject mappers and for people who just started mapping. If there is a clear scheme how to map similar things people would know: "Hey I have a proposed building so I'm going to tag it like proposed highways I already tagged before". This would spare people of lot of work for searching in the wiki and on taginfo. Thats why I think some form of standardization is necessary. For example when introducing new tags do you use tag:suffix or tag + extra tag. I think for such things some type of voting is important. The way Voting works atm is not satisfying. The Voting process is well hidden in the depth of the wiki. Voting processes should be made more prominent by showing them on the wiki start page, Editors and other places mappers use. Another problem in my opinion is communication. The rich possibilities for communicating in OSM is blessing and curse at the same time. With forum/wiki (discussion pages)/ mailing lists/ IRC/ help desk/ (Changeset Comments) we have good communication tools for every need. But the bunch of places also separates users from each other. I think there aren't so many who are watching multiple or all communication channels. Sometimes this leads to situations in which one part of the community isn't aware of the other part, which leads to confusions. Another thing I see is that it's really hard to change old tags because you may have to do a mechanical edit and and it's always very hard to convince all active mappers that this won't break everything. But in my opinion changing old tags that are used a lot sometimes might be necessary to improve OSM. In this case I think that "projects using this tag" of taginfo is very important. Data consumers should be encouraged to document their used tags so that they could be automatically notified when any changes in tagging happen. If all developers are notified in advance they would have the possibility to make their code changes and be ready for the day the new tagging starts. A defined time span and developer notification for bigger changes would weaken mappers argument that a change in tagging would break all there beloved apps and map styles. I'm aware that big mechanical edits are always critical. Just like now they should be well documented and tested.

Mapillary and cylceway tagging question 4 months ago

Nice...keep on the good work =)