<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">On 10/15/13 8:01 PM, Chris Lawrence
wrote:<br>
</div>
<blockquote
cite="mid:CANJCZGLbNorLeXZXK_POtKnmUSaf8rp568-NWUtW33oR2uBX7Q@mail.gmail.com"
type="cite">
<meta http-equiv="Context-Type" content="text/html; charset=UTF-8">
<div dir="ltr">
<div class="gmail_quote">
<div dir="ltr">
<div class="gmail_extra"><br>
<a moz-do-not-send="true"
href="http://en.wikipedia.org/wiki/Las_Vegas"
target="_blank"></a></div>
<div class="gmail_extra"><br>
</div>
<div class="gmail_extra">Defining an alt_name or loc_name of
"Las Vegas" on each of the surrounding CDP
boundaries/relations may help Nominatim geocode these
cases better. But the CDPs are not part of the city
(aside from any areas that may have been annexed, which
should be reflected in the new TIGER 2013 boundaries) and
should not be conflated with the city boundary.<span
class="HOEnZb"></span><br>
</div>
</div>
</div>
</div>
</blockquote>
right. whatever gets done with boundaries should be done on
something<br>
that at least tries to reflect facts, and not based on notions.
that's why<br>
i suggested going to TIGER 2013 as, while it may not perfectly
reflect<br>
the exact legal boundaries, it should be pretty close, as the Census<br>
Bureau does actually care about getting the headcounts right.<br>
<br>
richard<br>
<br>
<br>
<br>
</body>
</html>