I should clarify what I said under point 2. You can use barrier=kerb. But if this isn’t combined with kerb=lowered or kerb=flush, it implies, or defaults to, wheelchair=no. So if you add a kerb to a footpath, you really need to define the kerb type at the same time.

Thank you!

Hi there. Good work on all your pedestrian mapping! I hope you don’t mind me giving you a couple of points of feedback:

1. When curving road geometry, please consider the effect it will have on routing algorithms. For example, at the intersection of Eighth and Girraween, a driver may turn left or right onto Eighth, and drivers heading either direction on Eighth may turn onto Girraween. So flaring Girraween outwards at the intersection, as elegant as the curves are visually, will cause routing issues. To turn left onto Eighth, a driver might hear something like “merge right”. A routing algorithm may also deem a right turn onto Eighth to be impractical due to the extra sharp angle on the map. So the intersection should be as close to 90 degrees as possible to ensure it is treated as a T-intersection. To avoid similar misinterpretations, when a dual carriageway tapers to a single carriageway, it’s best to do so with a defined angle rather than trying to soften the angles.

2. Though adding kerb nodes at every pedestrian crossing may seem ideal for more complete data, it can have unintended consequences. This is telling consumers that there’s a barrier there, which will, for example, lead to routing software being unable to find a wheelchair-friendly route.

Thanks, Ewen.

Meant to say way #1420325115.

Hi there. Can you please share your source for mapping way way/1420325114 and the rest of this car park’s roads as dual carriageways? It doesn’t appear to match available aerial imagery, or my memory of the location. Apologies if I’m wrong.

Hi there. Thanks for fixing. Can you please explain what you mean by “superfluous oneway” so that I can do better next time? :)

Hi there. Thank you for editing the map. I agree with aharvey and fortera_au, especially if you were editing a region that was previously untouched on OpenStreetMap. But it’s important to always look at how things are mapped nearby and try to edit in harmony with that, both for consistency and to respect your fellow mappers.

Around Merredin, farmland bounded by public roads is usually a single property. From year to year, crop fields might be divided or merged, and sheep can get moved around too. So trying to map each individual field isn’t really helpful here for any real world applications, and I would argue that it’s creating a map that is going to need regular maintenance to keep it accurate. Better to just outline entire areas of farmland, up to their outer fence lines, until they’re interrupted by public roads or a rail corridor.

Also, think about the gaps created in between the fields you’re drawing with landuse=farmland. The tracks between fields, the creeks, and other features are still part of the farmland. So in my opinion it doesn’t make a whole lot of sense to leave those gaps.

Please understand that I don’t intend to be critical. I’m the only resident mapper in this area, so I’ve made it my mission to make the best map of Merredin I can. It’s great to have some help on that. But when I came across your work today (I’ve been focusing on north of Great Eastern Highway for quite a while) and noticed the separately drawn fields, hopefully you can understand that I was mildly alarmed to find it done in this manner for no reason except for the aesthetics of a video game. 😅 So I just wanted to add my two cents.

Moving on, I have some tips to help you with your mapping.

1. When you draw buildings in iD, press the “Q” key after you drawn it and tagged it as a building. That will perfectly square the corners so it doesn’t look wonky.

2. According to my research, the correct way to tag small bodies of water on Australian farms is as a pond.

3. Please refer frequently to the OSM Wiki. There’s so much to learn, and plenty of nuance in tagging norms from country to country.

Ahh okay. Thanks for the explanation. It’s too easy to not notice an existing relation on iD.

And thank you. Enjoy the rest of your evening!

If not, a u-turn would be legal under WA law.

Hi there. What’s your source for the no u-turn? Is there a new sign there?

Hi Daniel. I hope you’re well. Just letting you know that the two car parks you added near the intersection of Ederle Street and Boudicca Drive don’t actually exist anymore, as can be seen in my recent Mapillary capture of the area. I figured I’d let you know so that you can remove them, so you wouldn’t think I’m arbitrarily undoing your work.

I think referring to the process more correctly as "replacing dashes with hyphens in Opening Hours tag syntax" would be more self-explanatory and avoid the need to look at the wiki for clarification. Just my opinion.

Thank you for your work. Please just be aware that you should avoid publishing edits over a wide area in a single changeset (this changeset features edits in Sri Lanka and Australia).

From my smartphone GPS measurements over a number of days, I am quite certain that Bing imagery for Merredin should be offset 2 metres to the south. But I realised it's too big a job for me to correct such a large portion of the map single-handedly. Map accuracy to 2 metres is still good, so it seems best that I just continue tracing Bing imagery without any offset to avoid creating inconsistencies. Perhaps a mapper with more experience, or better tools in the future, will be able to offset the entire area?

changeset/146559341

From my smartphone GPS measurements over a number of days, I am quite certain that Bing imagery for Merredin should be offset 2 metres to the south. But I realised it's too big a job for me to correct such a large portion of the map single-handedly. Map accuracy to 2 metres is still good, so it seems best that I just continue tracing Bing imagery without any offset to avoid creating inconsistencies. Perhaps a mapper with more experience, or better tools in the future, will be able to offset the entire area?

changeset/146559341

From my smartphone GPS measurements over a number of days, I am quite certain that Bing imagery for Merredin should be offset 2 metres to the south. But I realised it's too big a job for me to correct such a large portion of the map single-handedly. Map accuracy to 2 metres is still good, so it seems best that I just continue tracing Bing imagery without any offset to avoid creating inconsistencies. Perhaps a mapper with more experience, or better tools in the future, will be able to offset the entire area?

changeset/146559341