Dankesehr für die schnelle Eintragung der neuen Fahrradspuren in der Johannisallee

Hi,
Judging from this network map though this extended route is not fully part of HSL, but only until Jokela:
https://hslfi.azureedge.net/globalassets/matkustaminen/tulostettavat-aikataulut-ja-kartat/reittikartat/liikennevalineittain/hsl_lahiliikennelinjat_pysty_700x1000_8_2021_paino.pdf
I am actually not sure how best to reflect partial network membership in a route relation. Breaking the route into separate routes for the HSL and a VR segments doesn't seem to make sense since these are operating as through services. Right now the Helsinki HSL network validator is failing because Tampere is not part of the bounding box of the network :P
https://cdn.organicmaps.app/subway/finland.html

See also a similar re-tagging CS exchange two years ago: changeset/82544338

Hi,
Thanks for updating the tagging. I wasn't aware that riverbank tagging has been deprecated. Great initiative and thanks for monitoring for quality assurance globally.

Comment should say Chennai instead of Delhi

Hi and thanks for your continued contributions to keep public transport in the Phoenix area well mapped.
Can you please elaborate why you re-tagged the PHX Sky Train ( https://en.wikipedia.org/wiki/PHX_Sky_Train ) infrastructure to a tram? Tram infrastructure in OSM is defined as (metal) tracks running mostly alongside roads: osm.wiki/Trams
The Sky Train though is a monorail infrastructure - or more specifically an automated people mover with a central guide rail. And in OSM the current established tagging for these is railway=monorail + monorail=rubber_tyres
I'd love to understand your motivation for the tagging update. Thanks in advance for taking the time

Stop areas are done: changeset/121845050

I'm on the task of creating stop areas already right now :)

Correction: Change in Incheon, not Seoul

Source was Maxar imagery

I didn't review all of the previous tags, but indeed artist_name seems to be what was meant by "author". Suur aitäh for fixing it.
I reviewed instances of historic=monument objects in Estonia based on http://www.historic.place/themes/monuments/ and only reviewed the primary tag, but should have also done a sanity check on the others.

Oh, wow. Thanks for fixing this eventually. No idea what I was thinking back then :P

Hi,

Thanks for the update to the Incheon metro line 2. Are you sure the light_rail tagging is appropriate for this infrastructure though? Here's why I think it should remain tagged as subway:
- Electrification is via third rail and not overhead line
- train capacity is higher than typical light rail lines
- station Infrastructure is already built for 4 car trains
I would consider Incheon line 2 a "light metro", but not a "light rail". See the definition here: https://en.wikipedia.org/wiki/Medium-capacity_rail_system

Therefor, I would recommend changing the tagging of infrastructure and lines back to subway.

Thanks for fixing this. I wasn't aware of this malfunction of the wikidata matcher, but makes sense if the brand on wikidata also has a coordinate location for the headquarter :(

I didn't change anything in regard to the under construction state of line 4 in this changeset. But it looks like meanwhile someone already updated the operational status of the tracks here, so we should be good now: way/933094508

Hi and thanks for reaching out.
This might have gotten lost in translation, but: I didn't consciously deleted "ownership" information with this change. Which object and which tag on that object are you referring to?

Hi,
Can you explain why you deleted the route relations I created for CRT Line 9?

Oups. Changeset comment should say "Xi'an" instead of "Wuhan".

Changeset comment should read:
Updated power tagging

Changeset comment should read:
Updated power tagging