<html>
<head>
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">On 08/02/19 20:37, Ulrich Lamm wrote:<br>
</div>
<blockquote type="cite"
cite="mid:EEA3DD1A-CB00-428A-8BE0-1F28A1FE5A7D@t-online.de">
<meta http-equiv="content-type" content="text/html;
charset=windows-1252">
<br>
<div>
<div>Am 08.02.2019 um 00:44 schrieb <a
href="mailto:tagging-request@openstreetmap.org"
moz-do-not-send="true">tagging-request@openstreetmap.org</a>:</div>
<br class="Apple-interchange-newline">
<blockquote type="cite"><span class="Apple-style-span"
style="border-collapse: separate; font-family: Helvetica;
font-style: normal; font-variant: normal; font-weight:
normal; letter-spacing: normal; line-height: normal;
orphans: 2; text-align: -webkit-auto; text-indent: 0px;
text-transform: none; white-space: normal; widows: 2;
word-spacing: 0px; -webkit-border-horizontal-spacing: 0px;
-webkit-border-vertical-spacing: 0px;
-webkit-text-decorations-in-effect: none;
-webkit-text-size-adjust: auto; -webkit-text-stroke-width:
0px; font-size: medium; "><br>
Message: 2<br>
Date: Fri, 8 Feb 2019 10:01:28 +1100<br>
From: Warin <<a href="mailto:61sundowner@gmail.com"
moz-do-not-send="true">61sundowner@gmail.com</a>><br>
To:<span class="Apple-converted-space"> </span><a
href="mailto:tagging@openstreetmap.org"
moz-do-not-send="true">tagging@openstreetmap.org</a><br>
Subject: Re: [Tagging] A general problem: Co-ordinate sets
vs.<br>
<span class="Apple-tab-span" style="white-space: pre; "> </span>background
informations<br>
Message-ID: <<a
href="mailto:0f90faea-b79f-668c-c887-035114856e55@gmail.com"
moz-do-not-send="true">0f90faea-b79f-668c-c887-035114856e55@gmail.com</a>><br>
Content-Type: text/plain; charset=utf-8; format=flowed<br>
<br>
I don't know what your trying to say here?<br>
<br>
<br>
This looks to me like either ;<br>
<br>
A) 'imported data cannot be changed'!<br>
The problem with that is the imported data may be wrong,
inaccurate of simply old.<br>
</span></blockquote>
It is necessary that imported geometries can be changed.</div>
<div>It is necessary that also other data can be actualized.</div>
<div>
<blockquote type="cite"><span class="Apple-style-span"
style="border-collapse: separate; font-family: Helvetica;
font-style: normal; font-variant: normal; font-weight:
normal; letter-spacing: normal; line-height: normal;
orphans: 2; text-align: -webkit-auto; text-indent: 0px;
text-transform: none; white-space: normal; widows: 2;
word-spacing: 0px; -webkit-border-horizontal-spacing: 0px;
-webkit-border-vertical-spacing: 0px;
-webkit-text-decorations-in-effect: none;
-webkit-text-size-adjust: auto; -webkit-text-stroke-width:
0px; font-size: medium; "><br>
B) 'imported data cannot be used'<br>
The problem here is that OSM looses a valuable and large
data source.<br>
Yes it can be 'wrong', 'old' and/or 'inaccurate' but it does
give a starting point for improvements.<br>
</span></blockquote>
<div>But for references on definitions, names, and scientific
mesurements of geographic objects,</div>
<div>it must be allowed to note "this value is from this
source", also if the source is not ODbL</div>
<div>And the provider (e. g. an official environment database)
has the natural right to be mentioned and to be cited
correctly..</div>
<div>Therefore OSM has to accept Creative Commons conditions for
such data.<br>
</div>
</div>
</blockquote>
<br>
No, OSM does not have to accept that. <br>
I think that is what this is leading too, ... Creative Commons data
cannot be used in OSM. Unless they meet OSM requirements - usually a
waiver. <br>
<br>
<blockquote type="cite"
cite="mid:EEA3DD1A-CB00-428A-8BE0-1F28A1FE5A7D@t-online.de">
<div><br>
<div>Courses and outlines of many natural objects are mapped
very roughly OSM.</div>
<div>Values derived from such mappings are incorrect, too, <br>
</div>
</div>
</blockquote>
<br>
Certainly some things are rough, that is not a factor of the quality
or reliability of the data that OSM has access to, but a time limit
of the mapper to make that entry. <br>
Given more time the mapper could make much better entries in to OSM
.. but they do have other things to do, like eat and sleep for
instance. <br>
All maps suffer the same constraints, time and money. <br>
Experienced map users realise that any map is a representation that
can be out of data, distorted or 'rough' in certain places and ways.
<br>
OSM gives a fair chance of being up to date and accurate due to the
number of local contributors. <br>
<br>
<blockquote type="cite"
cite="mid:EEA3DD1A-CB00-428A-8BE0-1F28A1FE5A7D@t-online.de">
<div>
<div><br>
</div>
<div>For some informations, OSM cannot be more correct than
offiical databases:</div>
<div>Official definitions may be optimal or suboptimal, but they
are valid.</div>
</div>
</blockquote>
They can be out of date. The definitions may not match public
perceptions of what it means. <br>
And they certainly don't have world wide coverage.<br>
<br>
<blockquote type="cite"
cite="mid:EEA3DD1A-CB00-428A-8BE0-1F28A1FE5A7D@t-online.de">
<div>
<div>Means of long timelines of measurements cannot be
substituted by single measurements in single visits.</div>
</div>
</blockquote>
<br>
Map users usually use the map over short time frames when on site,
so the accuracy of a single visit matches that of the map user. <br>
OSm does not claim to be surveyor accuracy. <br>
<br>
<blockquote type="cite"
cite="mid:EEA3DD1A-CB00-428A-8BE0-1F28A1FE5A7D@t-online.de">
<div>
<blockquote type="cite"><span class="Apple-style-span"
style="border-collapse: separate; font-family: Helvetica;
font-style: normal; font-variant: normal; font-weight:
normal; letter-spacing: normal; line-height: normal;
orphans: 2; text-align: -webkit-auto; text-indent: 0px;
text-transform: none; white-space: normal; widows: 2;
word-spacing: 0px; -webkit-border-horizontal-spacing: 0px;
-webkit-border-vertical-spacing: 0px;
-webkit-text-decorations-in-effect: none;
-webkit-text-size-adjust: auto; -webkit-text-stroke-width:
0px; font-size: medium; "><br>
<br>
Once in OSM it can be changed by anyone. Even fumble
fingered me. Usually errors are picked up and corrected.<br>
Even deliberate things that are wrong are picked up.<br>
<br>
</span></blockquote>
I had repeated the reasons for ODbL.</div>
<div>ODbL necessary for the import of geometries.</div>
<div>But if everything in OSM is ODbL, </div>
<div>OSM isolates itself form references (available under Creative
Commons conditions, only), which are essential for its
reliability.<br>
</div>
</blockquote>
<br>
OSM reliability rests with us and the sources OSM can use. <br>
<br>
Sources OSM cannot use, should not be used to make entries into OSM.
<br>
<br>
<br>
</body>
</html>