<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<title></title>
</head>
<body text="#000000" bgcolor="#ffffff">
I <i>think</i> I'm responsible for that big error in Hudson Bay.
I've fixed it, but can't quite figure out how two small mistakes
caused that big glitch. Perhaps the real problem is that the
coastlines are updated only a few times a year, I fixed the problem
as soon as I saw it, and yet it will persist on all levels. (I don't
know if this can be changed, don't interpret this as a demand or
passing of the blame for the error)<br>
<br>
In regards to the imports. I mostly import in areas without any
decent aerial imagery, or in some cases people (though in some cases
images came after the import) . If someone is willing to pay me to
map these areas (I don't mind donating time, but I need to eat/get
there) and give me good aerial imagery and a high quality GPS I will
swear off Canvec, but that doesn't seem likely. <br>
<br>
Sam Dyck<br>
<br>
On 11-12-02 04:56 PM, <a class="moz-txt-link-abbreviated" href="mailto:talk-ca-request@openstreetmap.org">talk-ca-request@openstreetmap.org</a> wrote:
<blockquote
cite="mid:mailman.29327.1322866584.26453.talk-ca@openstreetmap.org"
type="cite">
<pre wrap="">We could ban imports. But we still want to have access to external
sources. So let's start treating external like we treat aerial
imagery. When you do a foot survey you take notes and photos and draw
sketches. Then you map it by referring to your notes and photos and
sketches and aerial imagery. That's how we notice that the aerial
imagery is three years old doesn't show the new shopping plaza or
extension on the old mill. And we consider all of those sources then
take the best we can from every source and put it in OSM. That's why
OSM is so good where we have a rich community. OSM is better than any
other single source.
</pre>
</blockquote>
<br>
</body>
</html>