I have no idea. It was a name already tagged on the road and since I was only working to fix geometry errors and I couldn't tell or disprove that's a correct name I simply left it untouched.

I agree that it would be beneficial if we had a more detailed tag variation to capture APMs, but current mapping pratcie in OSM is to use monorail tagging for guided transport systems like most APMs:
Quote: "railway=monorail - Also used for monorail-like automated people-mover systems" from osm.wiki/Railways
Quote: "Mappers may also want to include driver-less systems that occur within some big airports for terminal transfer." from railway=monorail

The thinking behind this being that most - like Sengkang LRT - feature a central guiding rail and therefor have just one rail == monorail.
Have you thought about investing some time to form a proposal to capture diferent forms of APMs? Maybe we can collaborate?

Hi Michael,
It seems you somehow accodentially deleted the stop positions for the Expo line metro at Gateway stations. I've since added them back. Maybe you were confused because there are multiple station icons showing in your editor, but actually each metro station consists of a station node and stop positions on the actual track where the trains stop.

Can you please clarify what the "horrible changes" were that you corrected?
In your changeset I see that you re-tagged the unfinished western section of Line 2 from "proposed:*" to opened. Can you share why you did that?

I verified that it is an assisted living home:
https://www.wohnen-im-alter.de/einrichtung/pflegeheim/schemmerhofen/wohnpark-st-klara-23564

Hi and welcome to OpenStreetMap,

Thanks for your contributions to traced building outlines in Northern Tehran.
I spotted that you did connect a few building outlines to adjacent ways. This should be avoided as these objects are not physically connected unless the way leads to a parking entrance or passed through a building. It can happen easily during editing though thanks to the "snap to nearest way" functionality. Just be on the lookout for that.
You can see how I fixed this by moving he building nodes away from the ways'. Visualized here: https://osmcha.mapbox.com/changesets/68094146

Hi,
You have added an area feature with a few tags that look like they originate from another system. None are recognized within the OpenStreetMap project.
Would you mind reviewing the tagging, remove all that are irrelevant and add some that specify the area use?
From satellite imagery it looks like this could be a residential lot. So you could tag the outline with barrier=wall or the northern part with the building as building=apartments

Und die Brillenpinguine sind jetzt im Zoo Berlin während des Umbaus des Aquariums

Ah. Indeed. I totally overlooked these, because this is the established and documented standard for tagging the reference for runways. These are the first ten and hundred digits of the degree value of the runway heading. See aeroway=runway
Maybe we should teach OSMcha to not flag these...

Hm… i can't see where I added multiple values with a slash. I can see OSMcha complaining about it as well, but no pointer at which object it refers to. Any hint?

source for the tracing in this changeset was DigitalGlobe imagery

Das war schnell! Kudos.

Hello and welcome again to OpenStreetMap,
Thanks for your contributions. You added many ways from Bing satellite imagery. But you did not specify which type of way they are. To do that you need to add a highway tag. If these are roads in a residential area just tag them as highway=residential

You can find more information about highways in this wiki article in Persian:
osm.wiki/Fa:Highways

Hi and welcome to OpenStreetMap,
You added mosque, but didn't add the religion tag. For the place to be recognised as a mosque you need to add religion=muslim to "مسجد توحید". And to further specify either use denomination=shia or denomination=sunni

If the path is still visible on the ground I would agree with the current tagging. Is the access forbidden though? Or is it not advisable?

There were many directly imported GPS track which were not simplified. E.g. for a straight line between two points it contained 8+ nodes. I used JOSM's "Simplify way" to reduce geometry complexity. Since these were multiple 4x4 off-road tracks through the Kavir this resulted in 42K deletions over a few changesets.

There were many directly imported GPS track which were not simplified. E.g. for a straight line between two points it contained 8+ nodes. I used JOSM's "Simplify way" to reduce geometry complexity. Since these were multiple 4x4 off-road tracks through the Kavir this resulted in 42K deletions over a few changesets.

There were many directly imported GPS track which were not simplified. E.g. for a straight line between two points it contained 8+ nodes. I used JOSM's "Simplify way" to reduce geometry complexity. Since these were multiple 4x4 off-road tracks through the Kavir this resulted in 42K deletions over a few changesets.

There were many directly imported GPS track which were not simplified. E.g. for a straight line between two points it contained 8+ nodes. I used JOSM's "Simplify way" to reduce geometry complexity. Since these were multiple 4x4 off-road tracks through the Kavir this resulted in 42K deletions over a few changesets.

There were many directly imported GPS track which were not simplified. E.g. for a straight line between two points it contained 8+ nodes. I used JOSM's "Simplify way" to reduce geometry complexity. Since these were multiple 4x4 off-road tracks through the Kavir this resulted in 42K deletions over a few changesets.