<!DOCTYPE html><html><head><title></title><style type="text/css">#qt p.qt-MsoNormal{margin-top:0px;margin-right:0px;margin-bottom:0px;margin-left:0px;}
p.MsoNormal,p.MsoNoSpacing{margin:0}</style></head><body><div>I've started to summarise the general consensus to some of the import questions at <a href="https://gitlab.com/alantgeo/vicmap2osm#community-feedback">https://gitlab.com/alantgeo/vicmap2osm#community-feedback</a>.<br></div><div><br></div><div>Another thing is where someone has mapped an address with housenumber=2/5, but Vicmap is indicating it's unit 2 number 5, we convert this to addr:unit=2 addr:housenumber=5. This is slightly overstepping simply importing Vicmap data, to changing existing data in OSM (which mostly for the rest of the import, if OSM says something different we flag it for manual review), so I'm happy to also skip this.<br></div><div><br></div><div>However, given X/Y usually means unit/number, and then only where Vicmap data confirms this, and given addr:unit is a widely used tag for unit value, I feel it's probably best we do this.<br></div><div><br></div><div>Soon I'll share some links to actual maps and data that show exactly what would be changes so we can do more QA.<br></div></body></html>