unit from number create changeset from maproulette setTags operations

1 files changed, 7 insertions, 3 deletions

diff --git a/README.md b/README.md
index ab2febe..ccc336d 100644
--- a/README.md
+++ b/README.md
@@ -306,15 +306,19 @@ Split into the following candidate categories, then again split into suburb/loca
 
 The dedicated import account used for the import is [`vicmap_import`](https://www.openstreetmap.org/user/vicmap_import).
 
-
 ### Stage 1 - postal_code
-
 For background see [Inclusion of `addr:suburb`, `addr:postcode` and `addr:state`](#inclusion-of-addrsuburb-addrpostcode-and-addrstate).
 
 Using JOSM RemoteControl commands [`postal_code`](https://wiki.openstreetmap.org/wiki/Key:postal_code) will be added to the existing Victorian `admin_level=10` boundaries using the postcode derived from Vicmap Addresses. Except for Melbourne suburb because there are two postal codes in use, and the `postal_code` boundaries are already mapped.
 
+### Stage 2 - Set unit from housenumber
+During the conflation stage, Vicmap addresses which were deemed to match OSM addresses where in OSM it was represented as `addr:housenumber=X/Y` whereas in Vicmap it was represented as `addr:unit=X`, `addr:housenumber=Y`, then an automated tag change to move the unit into `addr:unit` is performed.
+
+This will be a single Victoria wide changeset.
+
+`bin/mr2osc.mjs` is the script which creates the OsmChange and uploads it as a changeset from the tag changes outputted from the _conflate_ stage as a MapRoulette `setTags` operation.
 
-### Stage 2 - 
+### Stage 3 - New addresses without conflicts
 
 `bin/upload.sh` is the script used to perform the actual uploads into OSM. For each import candidate (by candidate category by state) there is one OSM Changeset created.