Technically everything we map is *temporary*. I think 5 months is fine to map generally, especially in the case of roadworks and such; although, in this case, I think it's dubious to map railways as disused for such a short time span. Anyone who can travel over that railway probably knows it's disused without needing to check OSM, but marking it as disused will cause errors to flag in OSMI as the route relations are going over railways not in use.

From what I can tell, routers tend to update monthly at the longest, so that's the time period I would map lifecycle prefixes (only if I know I will update it when it changes again). Adding something that'll be there for a day or two -- which I've seen Lachlan do -- is not good for routing as it may be cached for upwards of a month or so. That should be avoided, ideally.

Please ensure that the ways in the route are in order (osm.wiki/Relation:route#Order_matters) and don't include ways on the wrong direction of travel.

I've fixed this route in changeset/181790595

Hi,

Thanks for contributing to OpenStreetMap.

When adding buildings and roads take care to check other (more up to date) aerial imagery sources to see if they still exist. Currently Esri World Imagery is the latest and shows that there are no buildings here:

way/1502723163/history#map=19/-37.880220/145.161261

I partially reverted those changes from your changeset:

changeset/181705547
changeset/181705578

Happy mapping!

Hi,

Again, it is preferable to use https over http for websites, especially when http autoredirects to https anyways. You should be copying the tags from the node to the building rather than doing it what appears to be manually. According to the wiki you can press "C" to merge nodes (what you are calling 'points') into ways (what you are calling 'areas')

way/1013602262/history/2 (incorrect website)
node/5374509961/history/3 (correct website)

If you have any questions, don't hesitate to ask.

Hi, thanks for contributting to OpenStreetMap.

If the website redirects to https from http it's preferable to add that.

Also please see osm.wiki/Keep_the_history . You are deleting the nodes with history while also not copying the tags properly (you appear to be doing it manually based on some of the website and phone tags I've seen). I'm pretty sure iD editor has some kind of merge functionality you could use.

Your check_date is in the future. Is this meant to be the opening_date?

Hi,

Thanks for contributing to OpenStreetMap.

Just letting you know in the case that this is accidental -- you've dragged a few address nodes away from their original locations. E.g:

node/12419417772/history
node/12412241208/history

Were those intentional?

You also seem to have connected a path and a power line together (node/13717800209). Nodes on power lines are generally meant to be poles.

Hi,

Thanks for contributing to OpenStreetMap.

Just letting you know that the name=* key should be used for the actual name of a thing and not be used in a descriptive manner.

Please see here for more information:

osm.wiki/Names#Names_are_not_for_descriptions
name=*

And here for how to address buildings addr:=**

proposed:building=yes is probably what you're looking for (proposed:=**)

Adding razed railway (especially nearly 30 years ago razed) is dubious and generally out of scope of OSM. We tend to map things that exist and are verifiable, but I understand that nonexistent railways are sometimes excepted from this rule.

While I'm not too familiar with this, I implore you to check out OpenHistoricalMap https://www.openhistoricalmap.org/about osm.wiki/OpenHistoricalMap, its for mapping things that have existed at any point within the world, even if they are long gone. I'm sure they'd love these kinds of contributions!

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