<div dir="ltr"><div><div>
<p style="margin:0in;font-family:Calibri;font-size:11pt">With these
discussions I want to make it clear what the LayerSearch plugin use is intended
for and what it is not.</p><p style="margin:0in;font-family:Calibri;font-size:11pt"><br></p>
<p style="margin:0in;font-family:Calibri;font-size:11pt">What it is:</p>
<p style="margin:0in;font-family:Calibri;font-size:11pt">1. It provides the
user the ability to search all layers and all fields against a particular
search string. It may be that the user already knows the layer he is interested
in, but that is not always the case. It is possible that the user has a number
of layers that contain similar data. I really do intend for it to search
multiple layers, but LayerSearch has the ability to select a single layer and
single column if desired.</p>
<p style="margin:0in;font-family:Calibri;font-size:11pt">2. It does not
require any pre configuration other than the search feature and whether you
want an exact match, a match at the beginning of a data field, or a match
anywhere in the data.</p>
<p style="margin:0in;font-family:Calibri;font-size:11pt">3. The resulting
matches display what layer and column the match was found in and by clicking on
the match QGIS will zoom to that feature.</p>
<p style="margin:0in;font-family:Calibri;font-size:11pt">4. While searching
on a large data set you can click an explore the found features even while it
is still searching.</p>
<p style="margin:0in;font-family:Calibri;font-size:11pt"> </p>
<p style="margin:0in;font-family:Calibri;font-size:11pt">What it is not:</p>
<p style="margin:0in;font-family:Calibri;font-size:11pt">The fastest search
engine in the world. It is not meant to be used to search a reference data set
like Quick Finder does. I would not want it to do any pre indexing or pre
configuration. That is not its purpose. I just tried a geonames data set with
2.2 million records,<span style="mso-spacerun:yes"> </span>LayerSearch
completed the task in 45 seconds on my laptop. That is acceptable to me. In the
mean time I was able to look at the matches it was finding. Even though I say
this, I am interested in optimizing it to be as fast as possible, but I don't
what the user to have to index the data or do any pre configuration first.</p>
<p style="margin:0in;font-family:Calibri;font-size:11pt"> </p>
<p style="margin:0in;font-family:Calibri;font-size:11pt">BTW when you talk
about moving to "Processing" what are you talking about? Are you
talking about the Processing toolbox or something else? I am new to the
development side of QGIS.</p>
<br></div>All the best,<br><br></div>Calvin<br><div><div><div><p style="margin:0in;font-family:Calibri;font-size:11pt"><br></p>
<div class="gmail_extra"><br><div class="gmail_quote">On Wed, Jun 8, 2016 at 2:20 AM, Denis Rouzaud <span dir="ltr"><<a href="mailto:denis.rouzaud@gmail.com" target="_blank">denis.rouzaud@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
<font size="-1"><font face="Verdana">Dear all,<br>
<br>
Indeed, the layer search offers something Quickfinder doesn't:
searching on all layers without any configuration, and the use
of operators.<br>
Although I think choosing an operator in a global search is not
very required (why doing price < 1000 on all layers, there is
a pretty good chance you know what layer you're looking for).<br>
<br>
From this, I think Michael's idea is pretty good. <br>
Make QuickFinder just a search bar in the application toolbar.
Then you can register any search process to it, which would be a
processing alg: might be OSM, FTS or Layer search.<br>
<br>
I would definitely be ok to do so for QuickFinder.<br>
But the question is when... It would take me a bit of time to
reorganize the plugin, make FTS generation and search as
processing algs (never done that before). I won't be able to
achieve this before August.<br>
<br>
So...is this fair to ask someone to wait that long for a dev and
then ask to modify its code to fit in? I have no answer, it's a
real question.<br>
<br>
<br>
Best wishes,<br>
Denis<br>
<br>
<br>
PS: yes, QuickFinder FTS search handles multiple columns as it
supports expressions (you can concatenate the columns).<br>
<br>
<br>
<br>
<br>
<br>
<br>
</font></font><div><div><br>
<div>On 06/07/2016 03:27 PM, kimaidou wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">
<div style="font-size:large">Hi all,<br>
<br>
</div>
<div style="font-size:large">I think it is
not really profitable to have multiple plugins. In my opinion,
efforts must be made to merge plugins when possible. In this
case, we have<br>
<br>
</div>
<div style="font-size:large">* Quick
Finder : Full Text Search is used here, which allows fuzzy
search, and is very efficient compared to scanning all
features for a match. A drawback, you must fill in the "FTS
vectors" for each layer you want to be able to search within.
I think it is not so bad because the process is fast. I also
think there is nothing preventing to add more than one field
in the search ( it is possible with FTS in PostgreSQL, must
also be the case with sqlite)<br>
<br>
</div>
<div style="font-size:large">* Layer
search : Great to have a quick way to search among all the
fields of all loaded layers, with no configuration. Drawback :
I think this can be very slow for big datasets, and it is not
"fuzzy", as regexp are used while iterating on each feature.
Another drawback : for external vector sources like
PostgreSQL, all features must been fetched !<br>
<br>
</div>
<div style="font-size:large">IMHO, the way
to go could be<br>
<br>
</div>
<div style="font-size:large">* Add the FTS
pregenerator of Quick Finder in Processing, as an alg
available for anyone to use<br>
</div>
<div style="font-size:large">* Add the FTS
search of Quick Finder as a Processing Alg<br>
</div>
<div style="font-size:large">* Add the
"layer search" worker as an Alg in Processing<br>
</div>
<div style="font-size:large">* Have a
combined plugin which let the user choose the search type :
FTS with pregeneration, or direct search with features
iteration. This will then run the corresponding alg<br>
<br>
</div>
<div style="font-size:large">Cheers,<br>
</div>
<div style="font-size:large">Michaël<br>
</div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">2016-06-07 7:16 GMT+02:00 Jeremy Palmer
<span dir="ltr"><<a href="mailto:JPalmer@linz.govt.nz" target="_blank">JPalmer@linz.govt.nz</a>></span>:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><span><br>
><br>
> I would personally prefer keeping it as a separate
plugin, but what do you<br>
> think? Should it be integrated with another plugin?<br>
><br>
<br>
</span>It seems like it has value over the other plugins.
Another issue I’ve had is searching all layer fields and
pushing the query filter down the provider (e.g PostGIS or
WFS) to increase the performance and usability. Using the
approach of iterating through all features client side with
a large dataset can be a killer in terms of bandwidth,
memory and time. Does your new plugin do that? If so then it
would be really useful :)<br>
<br>
<br>
<br>
This message contains information, which may be in
confidence and may be subject to legal privilege. If you are
not the intended recipient, you must not peruse, use,
disseminate, distribute or copy this message. If you have
received this message in error, please notify us immediately
(Phone 0800 665 463 or <a href="mailto:info@linz.govt.nz" target="_blank">info@linz.govt.nz</a>) and
destroy the original message. LINZ accepts no responsibility
for changes to this email, or for any attachments, after its
transmission from LINZ. Thank You.<br>
<div>
<div>_______________________________________________<br>
Qgis-developer mailing list<br>
<a href="mailto:Qgis-developer@lists.osgeo.org" target="_blank">Qgis-developer@lists.osgeo.org</a><br>
List info: <a href="http://lists.osgeo.org/mailman/listinfo/qgis-developer" rel="noreferrer" target="_blank">http://lists.osgeo.org/mailman/listinfo/qgis-developer</a><br>
Unsubscribe: <a href="http://lists.osgeo.org/mailman/listinfo/qgis-developer" rel="noreferrer" target="_blank">http://lists.osgeo.org/mailman/listinfo/qgis-developer</a></div>
</div>
</blockquote>
</div>
<br>
</div>
<br>
<fieldset></fieldset>
<br>
<pre>_______________________________________________
Qgis-developer mailing list
<a href="mailto:Qgis-developer@lists.osgeo.org" target="_blank">Qgis-developer@lists.osgeo.org</a>
List info: <a href="http://lists.osgeo.org/mailman/listinfo/qgis-developer" target="_blank">http://lists.osgeo.org/mailman/listinfo/qgis-developer</a>
Unsubscribe: <a href="http://lists.osgeo.org/mailman/listinfo/qgis-developer" target="_blank">http://lists.osgeo.org/mailman/listinfo/qgis-developer</a></pre>
</blockquote>
<br>
</div></div></div>
<br>_______________________________________________<br>
Qgis-developer mailing list<br>
<a href="mailto:Qgis-developer@lists.osgeo.org" target="_blank">Qgis-developer@lists.osgeo.org</a><br>
List info: <a href="http://lists.osgeo.org/mailman/listinfo/qgis-developer" rel="noreferrer" target="_blank">http://lists.osgeo.org/mailman/listinfo/qgis-developer</a><br>
Unsubscribe: <a href="http://lists.osgeo.org/mailman/listinfo/qgis-developer" rel="noreferrer" target="_blank">http://lists.osgeo.org/mailman/listinfo/qgis-developer</a><br></blockquote></div><br></div></div></div></div></div>