aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorAndrew Harvey <andrew@alantgeo.com.au>2021-05-19 22:27:55 +1000
committerAndrew Harvey <andrew@alantgeo.com.au>2021-05-19 22:27:55 +1000
commit00571f5f2e4d9cc60baf427c538b9407ab20fa57 (patch)
tree1777c13c9492bdba011e46e98a2b4173628e5c67
parent4685ecf3f9954a091fe86be3a195b3c2fd72a71d (diff)
community feedback to replace addr:city with addr:suburb
-rw-r--r--README.md1
1 files changed, 1 insertions, 0 deletions
diff --git a/README.md b/README.md
index e8facbb..ccfd4c1 100644
--- a/README.md
+++ b/README.md
@@ -201,5 +201,6 @@ Consultation with the local community on talk-au at https://lists.openstreetmap.
- Existing interpolation way addresses to be replaced with individually mapped address nodes.
- Imported addresses as lone address nodes, not merged onto existing buildings or other objects.
- Using `addr:suburb` as a catch-all for the placename/suburb/locality of the address, irrespective of if the value is actually referring to an OSM `place=suburb` or `place=town` or `place=hamlet` etc. (see page 25, section 15 of https://auspost.com.au/content/dam/auspost_corp/media/documents/australia-post-addressing-standards-1999.pdf)
+- Further to the previous point, where an existing address uses `addr:city` but our conflation indicates that the `addr:city` value should be `addr:suburb` then this will be updated on the existing object.
This is based on discussions to date, any of these points can be further discussed if needed.