Hi there, seems detaching the path from the peak that you moved didn't really work out.
I fixed this in my changeset changeset/55860192#map=14/33.8656/49.4512
Would be good if you could verify this makes sense now

Hi Chee Aun,
There's a difference between the public_transport=stop_position and the railway=station nodes. In a complete mapping for a subway station both exist and describe different features. The stop position is the location on one of the multiple tracks that a train in a certain direction stops. This is very useful information as when you use trains on the same line but in opposite directions you need to go to different stop positions in the station. As you see for a normal subway line station with two tracks for each direction you would already have two stop position nodes. Sometimes these stop positions have ref-tags as well, e.g. track 1 and track 2, but they differ from the station ref.

Additionally you would have either a node or an area for the building outline of the station. This is the OSM object that bears the station reference, e.g. ref=NS15 in case of Yio Chu Kang station.

These three nodes are combined using a public_transport=stop_area which you can find here: relation/7695977

So in fact 9 tags became 15 if you combine all the node and relation information. And as you can see the station reference is still left intact in the station node: node/206529415
btw. Maybe you can clear up if the amenity=bakery tag should remain on the station node. It looks like a tagging error.

Thanks

This was converting a previous tag "Bauausführung=Holz"

Sorry for that removal and thanks for fixing my "fix".

I'm very familiar with the multilingual tagging, thanks a lot for pointing this out.
If a name:* tag value is identical to the value already in the name tag than it's redundant. A name:* tag needs only be added if it differs. Do you agree?

Just to close the loop: I've meanwhile received updated imagery from apm-wa and am using this in combination with Mapillary and OSC imagery.

That section around Numaniyah is not a separated carriageway with two directional lanes. That's why I downgraded to primary.

Hi JaLooNz,
I hadn't finished reviewing the CCL line that's why it's station at Dhoby Ghaut was missing. Added this just today and you can see it part of the interchange relation stop_area_group here: relation/7695989

Hi Michael,
You added bakery tag to the Yio Chu Kang station via the Maps.ME app. Was this intential? I'd recommend to add a separate node at the location of the bakery inside the station grounds instead of adding it to the station node.

Hi Chee Aun,
I did preserve the ref-tag at the railway=station node. It won't be at the public_transport=stop_position node though. E.g. for Yio Chu Kang MRT station you will find it still intact here: node/206529415
Let me know if you find a station where I accidentially removed it. I couldn't find any while reviewing today.

Hallo Michael,
Soweit ich das weiss fahren dort ab und an noch Sonderzüge und die ÖPV-Infrastruktur wird noch gepflegt und vorgehalten. Siehe auch http://www.ris-sachsen.eu/CMS/index.php/strecken/nossen-freiberg
Da also dort noch ein Haltepunkt besteht würde ich public_transport=* weiter behalten.
Viele Grüsse,
Claudius

Thanks for the kind word. There's a few more stations that I need to review, but it already validates in most part here: http://osmz.ru/subways/brazil.html
This should mean that soon it will be routable in the Maps.ME app. Yay!

Indeed. This was already fixed meanwhile. Thanks for checking.

Why did you remove "Chitgar" station from the relation for Metro line 5?

I tend to disagree: I am not able to verify if this camp is accessible for wheelchair or not, but I could tell that the capitalization of this tag is most likely wrong. That's why I fixed the capitalization to lowercase. This is helpful in that it surfaces this object in whellchair related data outputs which is probably how you found this object as well. So my lowercase tagging update was helpful to surface that there might be a data issue when tagging a prison camp with wheelchair accessibility.

Why did you put the whole tracks of Tehran metro line 1 to railway=construction? e.g. ways way/206878117 and way/206878116 and so on.

This line is open since 2001 and is currently not undergoing any construction work.
Did your survey reveal anything otherwise?

Just looking at the parameters you mentioned it would qualify as commuter rail. But we are mapping the infrastructure and that is one of an express subway line. Everything is prepared for an additional at Vavan intermediate station. Also it was built as an extension of line 1. So everything is subway infrastructure. Following your argumentation the furthest you could go is adjusting the route relation, but everything on the ground should remain as subway.

Half of the buildings you added in nthis changeset are duplicates - from other buildings you added in this changeset as well. If you encounter problems uploading your changes (e.g. connection interruption) you might want to double check that you are not mistakenly uploading the same traces twice.

Most of the residential streets you added are duplicates from a previous changeset of yours. If you encounter problems uploading your changes (e.g. connection interruption) you might want to double check that you are not mistakenly uploading the same traces twice.