<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix"><br>
If you use the tool, you know that fixAddresses plugin (who
follows what the wiki told them) takes care of the postal code in
one simple click on the '"guess" button, the editor just needs to
verify them. The postalcode + street are the most important ones
to put on a building.<br>
</div>
<blockquote
cite="mid:CAJKJX-SaYHQJV1mEfiMGCjRzdfY_NWJNHU2FGK0R4EP=U3ZDxA@mail.gmail.com"
type="cite">
<div dir="ltr"><br>
<div class="gmail_extra"><br>
<br>
<div class="gmail_quote">On Tue, Apr 16, 2013 at 6:46 AM, Jo <span
dir="ltr"><<a moz-do-not-send="true"
href="mailto:winfixit@gmail.com" target="_blank">winfixit@gmail.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">
<div>
<div>I thought the consensus was that we repeat
addr:street for each house but not the other
information like addr:city, addr:postcode,
addr:country and whatnot. Imagine what happens to
the size of the DB (and all its derivatives like the
planet files), if everybody starts doing that for
each and every house/address in the world!<br>
</div>
</div>
</div>
</blockquote>
</div>
</div>
</div>
</blockquote>
That way you will end up with wrong postal codes for several
streets, after all -again-: it's not repeating, it's detailing the
data. I think you better stop worrying about the size of the data,
if people put in stuff like individual tree's and firehose's,
parking meters, amenity=bench using 2 nodes... I think it's ok to
put in way more interesting data like address data. It's not like
it's an extra node, it's a tag. <br>
<br>
I think the most wet dream for the openstreetmaps founders could
have in 2005 is having address data for every building in the
world. That is exactly what we are going for!<br>
<br>
Concerning the consensus, I can't find any stating we should limit
what we enter due to data size concerns. It's already huge as it
is, but so are cheap disks these days.<br>
<br>
<blockquote
cite="mid:CAJKJX-SaYHQJV1mEfiMGCjRzdfY_NWJNHU2FGK0R4EP=U3ZDxA@mail.gmail.com"
type="cite">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">
<div>
<div>
</div>
Potlatch has its limitations, but by choosing to work
with it, people indicate a willingness to live with
those limitations. I can only hope the IDeditor will
overcome those limitations one day and that all
Potlatch users will migrate towards it when it does.<span
class="HOEnZb"><font color="#888888"><br>
<br>
</font></span></div>
<span class="HOEnZb"><font color="#888888">Jo<br>
</font></span></div>
<div class="HOEnZb">
<div class="h5">
<div class="gmail_extra"><br>
</div>
</div>
</div>
</blockquote>
<div><br>
</div>
<div style="">+1 We should not map for the renderer, nor
for the (simpliest) editor.</div>
</div>
</div>
</div>
</blockquote>
+1<br>
<blockquote
cite="mid:CAJKJX-SaYHQJV1mEfiMGCjRzdfY_NWJNHU2FGK0R4EP=U3ZDxA@mail.gmail.com"
type="cite">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">
<div style=""> </div>
<div style="">+1 also on not repeating the same data over
and over.<br>
</div>
</div>
</div>
</div>
</blockquote>
-1<br>
<br>
We should also not map what we think is more convenient for us. We
should not map for the machine, but for the 'users', a broad term.<br>
<br>
Glenn<br>
<br>
</body>
</html>