[talk-au] Victorian Vicmap Address Import Proposal

Andrew Harvey andrew at alantgeo.com.au
Fri May 21 06:13:13 UTC 2021


> Please don't do that. Now that we have a complete set of admin_level 10 
> boundaries in Australia addr:suburb is now redundant.

This prompted me to see where the Vicmap suburb value differed from the OSM admin_level=10.

After excluding some special cases, there were 62 Vicmap addresses with a locality different to what we have in OSM. It looks like a bunch are bad Vicmap data, most of the rest are address points practically on the admin boundary line, there's only a small handful otherwise to deal with.

https://gitlab.com/alantgeo/vicmap2osm/-/jobs/1279647817/artifacts/raw/dist/vicmapSuburbDiffersWithOSM.geojson

My analysis supports it is mostly fine from a data consistency point of view to rely on the admin_level 10 suburb, except for a handful of cases (and even then it's not clear between Vicmap or OSM which is correct).

> Postcodes can be added once to the level 10 admin boundary or as a 
> separate postal_code boundary if they don't align.

Of the 2988 admin_level=10 suburb/localities in OSM:

- 2912 have only one distinct postcode from Vicmap data,
- 9 have >1 postcode from Vicmap
- a handful have no addresses

Of the 9 that have >1 postcode, 7 have only 1 address with a different postcode, 1 has only 3 addresses with a different postcode, and one suburb/locality (Melbourne suburb) has two main postcodes 3000 with 51,458 addresses and postcode 3004 with 12,158 postcodes. Then for the Melbourne case, it's clear than Melbourne CBD is 3000 and areas south 3004. We could add a separate boundary=postal_code for Melbourne.

My analysis supports adding postal_code to the level 10 admin boundary is safe for pretty much the whole state, except for Melbourne where we can add a postal_code boundary.

I'll follow up in another email about the other points raised.



More information about the Talk-au mailing list