junction=roundabout
is an appropriate tag for roundabouts, you don't need to tag oneway=yes with that as well

Hi,

Please do not attach serviceway nodes to the Suburban Rail Loop ways

Hi Gpapaniko,
Thanks for contributing to OpenStreetMap.

You may want to check the name=* wiki for guidance. The name key should not be used to describe things (osm.wiki/Good_practice#Don't_use_name_tag_to_describe_things) and should be the actual name of a given feature.

building=house is an appropriate tag to use for a house.

Happy mapping!

Hi, please try to keep changesets to one continent. It makes it harder to review if the bounding box is this large.

Generally, we're not meant to use the name key solely to make it easier to edit route relations (an exception I often see is the name of a route being descriptive and including "from => to" - though that is controversial as I understand it). I think the name "Platform [number]" is a better fit for the name=* key as it's the most common/used/known name for the platform. It's the name that the announcer uses when describing where a train is arriving/departing, and the name someone would probably give when asked "what is the name of this platform?". If you want to rename them, go ahead, but I think you should start a community discussion if you wish to continue renaming platforms in other stations, as we currently have two naming schemata

You've changed the naming scheme of the platforms here (Platform n -> Southern Cross n). While I disagree with this change, I think an individual naming schema should be applied consistently across the station. Currently it goes from "Southern Cross 14" -> "Platforms 15A...". Also, worth considering that most of the platforms in Melb train stations are named "Platform" rather than the name of the station. In fact, I'm pretty sure the only ones that use the station name were renamed by you

Please try and keep the history (osm.wiki/Keep_the_history). Rather than deleting something and "rebuilding" it, it is often better to modify what already exists. It makes it much easier for people to review your changes and also investigate the history of an object (some of the ways you deleted have history going back 7+ years)

Hi, the bus stops needn't go on the footpaths. It is fine to keep them where the pole is (usually by the tactile paving)

Hi, I have removed that one. It may take some time to show on the map due to browser cache.

Hi,

In this situation the crossing tag should have been removed rather than the node itself as it was part of a building way.

I've restored the building geometry in changeset/175133725

Instead of using oneway=-1 you can simply reverse the way. oneway=yes is much more intuitive than oneway=-1

oneway=-1

You've mapped some of these buildings as triangles which is incorrect. Most of these buildings should be rectangular. You should also press "Q" after drawing a building to orthagonalise its shape.
---
#REVIEWED_BAD #OSMCHA
Published using OSMCha: https://osmcha.org/changesets/174100154

Thanks for the tip, but it was slightly more complicated than that. I had to disconnect a node (ALT+J) from a few ways and one I couldn't do because I had to undelete a deleted node as well (I found a partial revert easier for that). Normal dragged nodes are easy enough to restore their location without a revert, I agree :)

What is this untagged way meant to be way/1446647689 and is this bus route (relation/16087037) meant to route over it?

Sorry, this was mean to be a comment for this changeset: changeset/174135730

The correct role for the bus stop in the route relation is "platform" rather than "bus_stop", and it should be ordered rather than appended to the bottom of the route

Here, you also added the stops to the route masters (osm.wiki/Relation:route_master). This is incorrect, as the route masters should only have members of the route variants on that line

I've reverted the problematic changes in https://overpass-api.de/achavi/?changeset=174088754.

Please take care not to accidentally drag and merge nodes

This needs to be reverted. Several dragged nodes, one with no obvious fix (deleted nodes, weird merges).

Reverting this changeset alone generates conflicts I couldn't resolve, so someone else will have to fix this.

As described in the other changeset, the stop positions are currently not ordered properly.