<!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">
So ogr layers would use return (after a query) shape->index as
the global/unique index and shape->tileindex as a tileindex? Or
would they stay as It is in 5.6 (use the shape->index as the
relative index from the query)?<br>
<br>
On 23/11/2010 4:43 PM, Lime, Steve D (DNR) wrote:
<blockquote
cite="mid:A7F7B3043D3BF0438F1206BAA3C9933C081EB30BF4@MNMAIL05.ead.state.mn.us"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1">
<meta name="Generator" content="Microsoft Word 12 (filtered
medium)">
<style><!--
/* Font Definitions */
@font-face
        {font-family:"Cambria Math";
        panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
        {font-family:Calibri;
        panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
        {font-family:Tahoma;
        panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
        {font-family:Consolas;
        panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
        {margin:0in;
        margin-bottom:.0001pt;
        font-size:11.0pt;
        font-family:"Calibri","sans-serif";
        color:black;}
a:link, span.MsoHyperlink
        {mso-style-priority:99;
        color:blue;
        text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
        {mso-style-priority:99;
        color:purple;
        text-decoration:underline;}
pre
        {mso-style-priority:99;
        mso-style-link:"HTML Preformatted Char";
        margin:0in;
        margin-bottom:.0001pt;
        font-size:10.0pt;
        font-family:"Courier New";
        color:black;}
span.k
        {mso-style-name:k;}
span.s
        {mso-style-name:s;}
span.EmailStyle19
        {mso-style-type:personal;
        font-family:"Calibri","sans-serif";
        color:windowtext;}
span.HTMLPreformattedChar
        {mso-style-name:"HTML Preformatted Char";
        mso-style-priority:99;
        mso-style-link:"HTML Preformatted";
        font-family:Consolas;
        color:black;}
span.EmailStyle22
        {mso-style-type:personal-reply;
        font-family:"Calibri","sans-serif";
        color:#1F497D;}
.MsoChpDefault
        {mso-style-type:export-only;
        font-size:10.0pt;}
@page WordSection1
        {size:8.5in 11.0in;
        margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
        {page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
<div class="WordSection1">
<p class="MsoNormal"><span style="color: rgb(31, 73, 125);">Drivers
that support tile indexes would continue to work “as-is”.
Those drivers aren’t database driven so they, like
shapefiles, would continue to use shape and tile indexes to
retrieve records for presentation. The only way adding an
additional index would make sense to me is if we relied on a
result set object and passed it to getShape() or
getFeature() in mapscript.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color: rgb(31, 73, 125);"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color: rgb(31, 73, 125);">Steve
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color: rgb(31, 73, 125);"><o:p> </o:p></span></p>
<div>
<div style="border-right: medium none; border-width: 1pt
medium medium; border-style: solid none none; border-color:
rgb(181, 196, 223) -moz-use-text-color -moz-use-text-color;
padding: 3pt 0in 0in;">
<p class="MsoNormal"><b><span style="font-size: 10pt;
font-family:
"Tahoma","sans-serif"; color:
windowtext;">From:</span></b><span style="font-size:
10pt; font-family:
"Tahoma","sans-serif"; color:
windowtext;"> Yewondwossen Assefa
[<a class="moz-txt-link-freetext" href="mailto:yassefa@dmsolutions.ca">mailto:yassefa@dmsolutions.ca</a>] <br>
<b>Sent:</b> Tuesday, November 23, 2010 2:28 PM<br>
<b>To:</b> Lime, Steve D (DNR)<br>
<b>Cc:</b> <a class="moz-txt-link-abbreviated" href="mailto:mapserver-dev@lists.osgeo.org">mapserver-dev@lists.osgeo.org</a><br>
<b>Subject:</b> Re: [mapserver-dev] RFC 65 - Single pass
query handling for 6.0<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Hi Steve,<br>
<br>
Regarding the use of tileindex as the shape index relative to
a query: would this work when users define <span class="k">TILEINDEX</span>
in their map file (I think that is what its is used for?)
Would it be better to have an additional new field?<br>
<br>
I really think that additional MapScript save/load queries a
la pre-5.6 are a welcome changes.<br>
<br>
regards,<br>
<br>
On 22/11/2010 12:42 PM, Lime, Steve D (DNR) wrote: <o:p></o:p></p>
<p class="MsoNormal">Hi all: I jotted down some thoughts on
changes I’d like to see made for 6.0 that address shortcomings
to the 5.6 single pass query<o:p></o:p></p>
<p class="MsoNormal">handling. I’m looking to simplify… We
have to do something for this release on the topic. I don’t
think the proposed changes will<o:p></o:p></p>
<p class="MsoNormal">take much effort.<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"> <a moz-do-not-send="true"
href="http://mapserver.org/development/rfc/ms-rfc-65.html">http://mapserver.org/development/rfc/ms-rfc-65.html</a><o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">Steve<o:p></o:p></p>
<pre><o:p> </o:p></pre>
<pre><o:p> </o:p></pre>
<pre>_______________________________________________<o:p></o:p></pre>
<pre>mapserver-dev mailing list<o:p></o:p></pre>
<pre><a moz-do-not-send="true" href="mailto:mapserver-dev@lists.osgeo.org">mapserver-dev@lists.osgeo.org</a><o:p></o:p></pre>
<pre><a moz-do-not-send="true" href="http://lists.osgeo.org/mailman/listinfo/mapserver-dev">http://lists.osgeo.org/mailman/listinfo/mapserver-dev</a><o:p></o:p></pre>
<p class="MsoNormal"><span style="font-size: 12pt; font-family:
"Times New Roman","serif";"><br>
<br>
<br>
<o:p></o:p></span></p>
<pre>-- <o:p></o:p></pre>
<pre>----------------------------------------------------------------<o:p></o:p></pre>
<pre>Assefa Yewondwossen <o:p></o:p></pre>
<pre>Software Analyst <o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Email: <a moz-do-not-send="true" href="mailto:yassefa@dmsolutions.ca">yassefa@dmsolutions.ca</a> <o:p></o:p></pre>
<pre><a moz-do-not-send="true" href="http://www.dmsolutions.ca/">http://www.dmsolutions.ca/</a><o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>Phone: (613) 565-5056 (ext 14)<o:p></o:p></pre>
<pre>Fax: (613) 565-0925<o:p></o:p></pre>
<pre>----------------------------------------------------------------<o:p></o:p></pre>
<pre><o:p> </o:p></pre>
</div>
</blockquote>
<br>
<br>
<pre class="moz-signature" cols="72">--
----------------------------------------------------------------
Assefa Yewondwossen
Software Analyst
Email: <a class="moz-txt-link-abbreviated" href="mailto:yassefa@dmsolutions.ca">yassefa@dmsolutions.ca</a>
<a class="moz-txt-link-freetext" href="http://www.dmsolutions.ca/">http://www.dmsolutions.ca/</a>
Phone: (613) 565-5056 (ext 14)
Fax: (613) 565-0925
----------------------------------------------------------------
</pre>
</body>
</html>