<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /></head><body style='font-size: 10pt; font-family: Helvetica,Arial,sans-serif'>
<p>Greg, regarding temporary duplication - Is your concern that the project will be abandoned midway through, leaving unreviewed data? Not sure why I didn't think of this earlier, but deduplication could conceivably be done by hand in JOSM before the upload occurs.</p>
<p>I agree that in this scenario, maximizing automation (combining address points with buildings, deduplication, etc) has its benefits. My only objections to that are the developer time and the increased potential for issues to slip through the cracks unnoticed. I'll do some deeper searching into the past imports list and see if I can find an existing solution.</p>
<p>Jacob</p>
<div id="v1v1v1_rc_sig"></div>
<p><br /></p>
<p id="v1v1v1reply-intro">On 2022-10-05 20:14, Greg Troxel wrote:</p>
<blockquote type="cite" style="padding: 0 0.4em; border-left: #1010ff 2px solid; margin: 0">
<div class="v1v1v1pre"><br /> Conflation: This will be an issue since a small portion of buildings<br /> in Cache Valley already have address information. However, since<br /> addresses should be manually combined with building outlines anyway,<br /> temporarily having a few duplicates is OK.<br /><br />I don't think it's ok. I think someone should figure out how to do this<br />programmatically, and that all the people doing address imports might<br />collaborate, or steal code from previous address imports.</div>
<br />
<div class="v1v1v1pre">_______________________________________________<br />Imports mailing list<br /><a href="mailto:Imports@openstreetmap.org" rel="noreferrer">Imports@openstreetmap.org</a><br /><a href="https://lists.openstreetmap.org/listinfo/imports" target="_blank" rel="noopener noreferrer">https://lists.openstreetmap.org/listinfo/imports</a></div>
</blockquote>
</body></html>