<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /></head><body style='font-size: 10pt; font-family: Verdana,Geneva,sans-serif'>
<p>On 2020-02-09 04:26, Joseph Eisenberg wrote:</p>
<blockquote type="cite" style="padding: 0 0.4em; border-left: #1010ff 2px solid; margin: 0">
<div class="pre" style="margin: 0; padding: 0; font-family: monospace"><br />
<blockquote type="cite" style="padding: 0 0.4em; border-left: #1010ff 2px solid; margin: 0">Re: "on a government map, by legal / statutory decree, from data authoritatively published on a website"</blockquote>
<br /> These examples are not "good practice" sources for openstreetmap.<br /> While many mappers import data from such sources, there is no "value<br /> added" in the case that mappers are unable to confirm if the<br /> government or "authoritative" data is accurate or inaccurate. Since<br /> the data in Openstreetmap can be changed at any time, and often by<br /> mistakes caused by new mappers, the authoritative database or source<br /> will always be better for database users to consult directly, unless<br /> openstreetmap can improve the originally imported data by checking it<br /> against reality.</div>
</blockquote>
<div class="pre" style="margin: 0; padding: 0; font-family: monospace"> </div>
<div class="pre" style="margin: 0; padding: 0; font-family: monospace">I beg to differ. Importing positions of accurately and authoritatively surveyed objects gives us calibration points for our more manual work. We are all warned about distortions and offsets in aerial imagery, and 99% of our on-the-ground mappers will be using consumer-grade GPS. If the location of an admin boundary has been surveyed to centimetre accuracy as lat X / lon Y, the presence of this in the OSM database, plus an indication of its authoritative source, gives an invaluable frame of reference. If Joe Bloggs comes along with his smartphone and locates it at X+dX,Y+dY he needs to understand that it is he who has the inferior data, and he should refrain from "improving" OSM by changing the location of the boundary. If other objects like rivers, highways etc should probably coincide with the admin boundary but don't, Joe Bloggs needs to consider that the professionally surveyed data is more likely to be correct before moving the admin boundary in OSM to fit his imperfect data.</div>
<div class="pre" style="margin: 0; padding: 0; font-family: monospace"> </div>
<div class="pre" style="margin: 0; padding: 0; font-family: monospace">Besides, OSM strives not only to be "complete" but also "useful". If imports can increase the usefulness of OSM, it is likely to positively impact its adoption. So what's not to like?</div>
<div class="pre" style="margin: 0; padding: 0; font-family: monospace"> </div>
<div class="pre" style="margin: 0; padding: 0; font-family: monospace">A subject often ignored in OSM is defining what me mean by "data quality." Quality is always relative to some definition of perfection. Is a point entered by an "OTG mapper" with a smartphone, of higher quality than a definitive, authoritative survey?</div>
<div class="pre" style="margin: 0; padding: 0; font-family: monospace"> </div>
<blockquote type="cite" style="padding: 0 0.4em; border-left: #1010ff 2px solid; margin: 0">
<div class="pre" style="margin: 0; padding: 0; font-family: monospace"><br /> Remember, this is the "good practice" page we are talking about<br /> editing, not the "how things really are done" page: we want to focuse<br /> on the "Gold Standard", best practices.<br /><br /></div>
<div class="pre" style="margin: 0; padding: 0; font-family: monospace"> </div>
</blockquote>
<div class="pre" style="margin: 0; padding: 0; font-family: monospace">Irrespective of the discussion above, Best Practises and Gold Standards can often usefully be illustrated by negative examples. Standards have quality too! A good standard will be unambiguous; one that is vague and open to a lot of interpretation is not a good standard.</div>
<div class="pre" style="margin: 0; padding: 0; font-family: monospace"> </div>
</body></html>