No worries, based on that photo it looks like the service road is no longer there so all good.

Thanks. Just a tip that while lanes=3 is still okay, it is ambiguous with respect to how many lanes in each direction. When it's an even number you can default to an even number in each direction, but not when it's odd. So in this case it can be helpful to add lanes:forward=X and lanes:backward=X depending on which direction the way is.

also I noticed you've deleted https://osmlab.github.io/osm-deep-history/#/way/702219833 it might have changed recently, so maybe you can confirm but there did used to be a service road here for one of the driveways to exit out onto Bathurst street you can see the arrow on the road at https://www.mapillary.com/app/?lat=-33.87412222222224&lng=151.20692222222215&z=19.58287877887588&pKey=kZzz6HFF5SkfutV5PDjYHw&focus=photo&x=0.28491036517820095&y=0.5103073083519546&zoom=0.870639500132132

highway=pedestrian highway=pedestrian " is a road or an area mainly or exclusively for pedestrians in which some vehicle traffic may be authorized (e.g. emergency, taxi, delivery, ...)". Pitt Street Mall is a good example since it's mostly for pedestrians but during certain hours of the data delivery drivers can use it as a road. Are you sure these small segments of footway which connect the sidewalk to the platform are best mapped as roads or should they simply be highway=footway?

In my opinion saying the destination:ref here is T2 is not quite correct. T2 means it's a transit lane, ie. requiring two occupants in the vehicle to use it, ie. what other jurisdictions and what OSM calls a hov lane. It's not a destination ref like the highway or road reference. On the other hand I guess you are keeping left and following that transit lane to the left.

If this is your company office, you should also add the tag office=company. office=company

I've added back into the route now.

Hi, welcome to OSM. Thanks for contributing.

In your edit here, keep in mind that tagging something as a building means the geometry should match the building footprint only, not the backyard as well.

If you only want to tag the whole property and not the building footprint then you can just add the address as either a point or a way covering the whole property without the building tag.

Hi could you please explain the reasoning for removing the service tag from the route relation?

According to osm.wiki/Public_transport#Railways service=commuter is the correct tag for urban mass transit systems with short headways (which is what the Northwest Metro mostly is).

PS. I did already had platforms roughly mapped as lines (not as accurate as your data though), it's better practice to reuse those existing ways when improving them rather than deleting them and starting afresh. I know it's not always possible though, but if possible it's better.

For https://osmlab.github.io/osm-deep-history/#/way/173170861 where you've added footway=no what was the intention there?

To say that pedestrians aren't allowed here you can use foot=no (but it's implied already because of access=no), or to say there is not footpath parallel to this road you'd use sidewalk=no or sidewalk=none.

ps to tag a service road as in construction you either need to do construction:highway=service OR highway=construction + construction=service. You've missed the highway=construction here, and in a few other places. I've fixed it now.

Thanks. Agreed with @SK53, I've used disused for now, once the chains have been removed can be updated to demolished or removed.

Okay I've marked this as a common pending a more information and updated the etymology tags in changeset/76279583

>robe data isn't enough to justify this, I checked on the ground and there is no signage or physical barrier indicating this restriction.

In this changeset it looks like you changed Garigal Road from a single way to two parallel ways (dual carriage), however lacking a physical barrier for most of the road it's better mapped as a single way, I've changed it back.

Hi, It looks like the wikipedia/wikidata links are for the person this is named after not the actual square. In that case see name:etymology=* for the correct tags to use.

Also because you're lacking a physical tag, can you say anything more about what this is? Is it a pedestrian area, a showground, a theatre or just an open grass space?

Ha I've seen tagging for the renderer, tagging for the router, but never tagging for the editor UI in this way before. I think it's better addressed by the editor UI being smart and generating a name like this based on the relation type.

I mean it's not harmful how you have it, since the name tag shouldn't really mean anything in this context.

Thanks, I updated one of these restrictions to simply except=bus instead of except=psv as per the sign https://www.mapillary.com/map/im/9mbQx7OPz81_3dFNfvv2fQ this only excepts busses not other psv vehicles like taxis. Is that right?

Oh yeah please feel welcome to keep up with your contributions.

In this case, even though bicycles are allowed here, it's still a footpath on the ground from a pedestrian perspective. We have this tag footway=sidewalk which says this footway is a sidewalk since it runs alongside the road, it's useful for some downstream data users.

So just because bicycles can also ride here, doesn't change the fact that it's a "sidewalk" footway. I see now you've added that footway=sidewalk tag back in thanks.

However at https://osmlab.github.io/osm-deep-history/#/way/530746983 you've added cycleway=sidepath, was that something you found documented somewhere? footway=sidewalk should be enough.