aharvey's Comments
| Changeset | When | Comment |
|---|---|---|
| 53194586 | Agreed both styles (separate way and sidewalk tags) can coexist. |
|
| 47583001 | I'm not sure about this... For example City of Sydney relation/1251066 you changed the name from "City of Sydney" to "Council of the City of Sydney". According to name=* the name tag is for the common name which I think should be "City of Sydney". It's what most people know it as and what the council use on most correspondence. See Australia as another example relation/80500, it's name is "Australia" even though it's official name is "Commonwealth of Australia" https://en.wikipedia.org/wiki/Australia. I think we should apply the commonly used name like "City of Sydney" for name (instead of alt_name), the full name like "Council of the City of Sydney" as official_name and "Sydney" as short_name (as it is in this case). |
|
| 52171535 | This edit is incomplete, if you move the railway station from this building to a node then could you move across all the tags including name, wikidata etc. as they are not correct now that way/461677979 not a railway station. You also need to update the way/461677979 was part of. |
|
| 52968904 | The phone number should be in the format +61 2 9XXX XXX. |
|
| 53027370 | It says at osm.wiki/Australian_Tagging_Guidelines#Roundabouts that roundabouts should be mapped out as circular ways. But I don't have an opinion on this and certainly as a node is better than not at all. |
|
| 53028123 | If you know the post office is here did you wanted to deleted the one at node/3146751111 ? The other one lists a copyrighted source, so happy to delete it over yours. |
|
| 53141650 | PS you could also add name:etymology=* |
|
| 21929178 | Hey, just a tip. Since these residential lots share borders in reality, the ways should share nodes so there are no gaps in between. PS. the building=house tag is for the building footprint, which is why these were changed to landuse=residential. |
|
| 52863402 | What's the policy on SEO edits, I encounter them almost every day and not really sure what to do. The ones I encounter it's a new OSM account for each "customer" and they never use the correct format for opening_hours or accepted payments etc. |
|
| 28621836 | Is it really named "indistinct track"?
|
|
| 53066927 | Hi, welcome to OSM! I'd suggest you take a look at these tags. They are much more widely accepted (about 5000 places tagged that way already in OSM) and mean people interested in fishing and scuba will be able to find this place as it will show up in their searches etc. osm.wiki/Tag%3Asport%3Dscuba_diving
These tags would replace your tourism tag. |
|
| 53029195 | PS. maybe also try editing in JOSM, personally I find it easier to deal with relations compared with the iD editor. |
|
| 52921848 | If they lead to a private property I've marked them access=private when I've mapped, although strictly only past the front fence is private. |
|
| 13600970 | no problem. done in changeset/52944761 |
|
| 13600970 | ||
| 13600970 | With relation/2521345 any reason why you've used except=psv? From the signage it should be except=bus? |
|
| 52845601 | @Daryl Radivokevic Unfortuantly the iD editor doesn't warn you when your changes affect a relation, so just try to watch out for how changes will affect relations too. When you go to save your changes in iD it will list what's changed and if it lists relations that you didn't intend to change you can double check. Personally I find JOSM osm.wiki/JOSM easier for this as it warns that your changes will affect a relation. |
|
| 46395396 | Hmm I feel it's redundant as it's no different to most other intersections in OSM right? I don't think it makes sense to have a no-u-turn relation on every single intersection unless signposted. |
|
| 46395396 | ||
| 46395396 | Sorry that's a bad example since I re-purposed your relation. See any of these
No uturn restrictions from and to the same way. |