[Discussion] Premature activation of LRT3 transit tags by zh9567

Hi everyone. I am opening this thread to discuss a recent mapping issue regarding the LRT3 Shah Alam Line development. I noticed that a veteran mapper, zh9567, has taken the liberty of unilaterally removing the construction tags and marking all LRT3 stations as fully operational before it’s finally opening for services. I have already left a comment on their specific changeset ( Changeset: 182065697 | OpenStreetMap ) and sent them a PM to address this, but I want to bring this to the community’s attention so we can agree on how to handle it.

​I can understand that the station buildings physically look completed on the ground and might not seem to be under active construction anymore. If the intention is to reflect the physical reality of the structures, it is perfectly acceptable to tag the buildings themselves as building=train_station instead of building=construction. However, we must draw a clear line between physical completion and operational status. The fact that a building is structurally finished does not mean it is providing a public transport service. Prasarana and RapidKL have not officially launched passenger services yet, and the line is strictly not open to the public, therefore it’s not right to pre updated it and also without community consensus.

Refer this also:

​According to OSM Wiki guidelines on lifecycle prefixes, we should separate the physical structure from its functional purpose. Tagging these locations as active railway=station and public_transport=station right now is factually incorrect and dangerous for downstream data users. It will immediately cause routing engines e.g. OSMand and Organic Maps and navigation apps to mistakenly direct commuters to closed facilities. The transit and railway functions must remain inactive. The correct approach is to use lifecycle prefixes like construction:railway=station or keep railway=construction, potentially adding access=no and an opening_date to make it clear that the transit nodes are not yet active.

​We cannot allow transit infrastructure to be prematurely activated based on physical appearance alone before the official service launch. I hope we can discuss this here to reach a final community consensus. If we do not hear back from zh9567 or if the tags are not self-corrected soon, I propose that we proceed to revert the functional transit tags to fix this error and restore the accurate lifecycle status. Please share your thoughts on this so we can finalize our next steps. Thank you.

Appendix: latest station name and code of Shah Alam Line

1 Like

@Zh9567 , it will be great to hear your views.

My view is that the value construction for any object should remain as construction until it is open for the general public to use. That is why the opening_date=* is an additional key for any objects under construction. When the object is open to the public, the opening_date key can be removed and the value construction changed to the value of the object.

1 Like

This has been resolved on this changeset.

1 Like