<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#ffffff">
On 10/25/10 2:58 PM, Emilie Laffray wrote:
<blockquote
cite="mid:AANLkTim4PMAW35rH5Lnry2c6zAV+Hof1jv1FtSjmVJmU@mail.gmail.com"
type="cite"><br>
<br>
<div class="gmail_quote">On 25 October 2010 12:49, Mike N. <span
dir="ltr"><<a moz-do-not-send="true"
href="mailto:niceman@att.net">niceman@att.net</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt
0.8ex; border-left: 1px solid rgb(204, 204, 204);
padding-left: 1ex;">
<div style="padding-left: 10px; padding-right: 10px;
padding-top: 15px;" name="Compose message area">
<div>> Multiple is_in=* tags.<br>
<br>
<font face="Arial" size="2"> How is this different from
the normal argument that is_in is obsolete because the
object is contained within an admin boundary and the
applicable is_in can be derived during a geo-query?</font></div>
</div>
</blockquote>
<div><br>
+1<br>
If a polygon exists, the is_in information can be inferred
easily through a small preprocessing.<br>
</div>
</div>
</blockquote>
it's not small preprocessing if you're trying to do some bulk
operation.<br>
<br>
computing geometric intersections/containment is no big deal for
small<br>
data sets, but scales damn poorly.<br>
<br>
richard<br>
<br>
</body>
</html>