The City of Melbourne has provided open data detailing 63617 address points
This import will gradually add address points throughout the City of Melbourne, merged with existing data.
Imports will be performed after local community revision of both the data set and the actual data contained into OSM.
- Source: https://data.melbourne.vic.gov.au/Property-Planning/Address-Points/a7rp-xtya
- Explicit permission: data.melbourne.gov.au explicit permission
The dataset will be imported incrementally via JOSM, preferably street by street.
Quality of the data
The data appears to be very granular, and already roughly aligned to OSM naming conventions.
One key difference to existing data is the placement of address nodes as close as possible to the nearest highway, ie not dissimilar to a 'letter box' placement. This may be slightly different to existing building geometry which places address notes further back from street level.
Sample of data: http://imgur.com/a/5F2JA
At the moment, address data includes every point at the level of individual land parcels, as opposed to aggregated addresses ("1-3 Example Street"). Where an existing aggregated address exists, this would be used in favour of individual plots (it more closely reflects what would is on the ground)
Several steps have to be executed in order to obtain data consistency thus reducing the amount of QA work to be done post import.
address_pn=131 Nicholson Street Carlton easting=321696.71094762 gisid=23453.0 latitude=-37.79732649 longitude=144.97481614 northing=5814739.92724131 str_name=Nicholson Street street_id=931.0 street_no=131 suburb=Carlton suburb_id=585.0
- Removal of: source_id, suburb_id, add_comp (contains name like attributes), lat/long, east/northing, gisid, address_pn
- Mapping of street_no => addr:housenumber, str_name => addr:street, suburb => addr:city
<node id='-37587' action='modify' visible='true' lat='-37.81682006247' lon='144.98764945281'> <tag k='addr:city' v='East Melbourne' /> <tag k='addr:housenumber' v='65' /> <tag k='addr:street' v='Wellington Parade' /> </node>
The following Overpass query will be used to download the existing house numbers into a new osm file:
<osm-script> <query into="<Name of the City>" type="area"> <has-kv k="admin_level" v="8"/> <has-kv k="name" v="<Name of the City>"/> </query> <union> <query type="node"> <area-query from="<Name of the City>"/> <has-kv k="addr:housenumber"/> </query> <query type="way"> <area-query from="<Name of the City>" /> <has-kv k="addr:housenumber"/> </query> <query type="way"> <area-query from="<Name of the City>" /> <has-kv k="addr:interpolation"/> </query> <item/> <recurse type="down"/> </union> <print mode="meta" /> </osm-script>
All existing address nodes will be kept. Missing tags listed in #Tagging Plan will be added wherein necessary. JOSM's Conflation plugin will be used to conflate the existing data with the new dataset.
In case of import problem the changeset will be reverted using the JOSM Reverter Plugin.
The following tags will be used on each address node:
addr:housenumber: formatted accordingly to #Address format;
addr:street: formatted accordigly to #Name Standardization of the highways;
addr:city: name of the considered suburb if present
Dedicated upload account
- http://qa.poole.ch/ will be used to track progress
- Given manual review in JOSM per street, the post import QA should be minimal
- Mapillary imagery will be used where possible to spot check address data, in combination with on the ground survey of small areas by the local community