When you say "encode the search queries accordingly" do you mean leave off
the spatial filter entirely? That won't work in my case, there is too much
data to not use an index. I think what I want is a way to force the use of
another geometry column (but this seems like it would have to be a bit of a
hack - ie. look around to see if there was another geometry column
available and use that).
This sounds a bit like your second suggestion. A bbox query against the
"original geometry" would work I think. Not sure how you would identify
the "original geometry" though? It would have to be present in the SQLView
columns, presumably - and then determined by just assuming the "other
geometry column" was the one to filter against? Or would require UI/model
changes to allow user to pick which geometry column is to be filtered by.
Or, drastically generalize SQLViews to allow user to fully specify the
emitted query, substituting WMS_EXTENT parameters into his own custom SQL
(+1 for this!)
On Tue, Mar 10, 2015 at 11:32 AM, Andrea Aime <[email protected]>
wrote:
> On Tue, Mar 10, 2015 at 7:27 PM, Martin Davis <[email protected]> wrote:
>
>> Well, good that there's an issue for this.
>>
>> I don't understand how the SQL can be changed to not require a spatial
>> index? What I'm suggesting is a way to use the spatial filter on the
>> underlying geometry, but return a different geometry column. Not sure if
>> this is possible in the current GS architecture?
>>
>>
> It is, you just have to figure out that your column is built at runtime by
> the virtual table definition, and thus does not have a index, and encode
> the search queries accordingly.
> Virtual table is just a special case of not having a spatial index (the
> other being having a real table without a spatial index).
>
> But yes, you cannot query the original geometry because GeoServer cannot
> know how your computed geometry relates to the original geometry, and
> Oracle does not know either afaik.... I believe other software allows you a
> special parameter where you could embed a simple bbox query against the
> original data... but that is really simpleton, in GeoServer we don't just
> have bbox searches... but maybe
> we could have some logic that tries to map back the query down to a bbox
> one, and have a primary filter/secondary filter approach (thus, keeping the
> real query against the computed geometry, but injecting a simple bbox one
> against the original geometry too)
>
> Cheers
> Andrea
>
>
> --
> ==
> GeoServer Professional Services from the experts! Visit
> http://goo.gl/NWWaa2 for more information.
> ==
>
> Ing. Andrea Aime
> @geowolf
> Technical Lead
>
> GeoSolutions S.A.S.
> Via Poggio alle Viti 1187
> 55054 Massarosa (LU)
> Italy
> phone: +39 0584 962313
> fax: +39 0584 1660272
> mob: +39 339 8844549
>
> http://www.geo-solutions.it
> http://twitter.com/geosolutions_it
>
> *AVVERTENZE AI SENSI DEL D.Lgs. 196/2003*
>
> Le informazioni contenute in questo messaggio di posta elettronica e/o
> nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il
> loro utilizzo è consentito esclusivamente al destinatario del messaggio,
> per le finalità indicate nel messaggio stesso. Qualora riceviate questo
> messaggio senza esserne il destinatario, Vi preghiamo cortesemente di
> darcene notizia via e-mail e di procedere alla distruzione del messaggio
> stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso,
> divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od
> utilizzarlo per finalità diverse, costituisce comportamento contrario ai
> principi dettati dal D.Lgs. 196/2003.
>
>
>
> The information in this message and/or attachments, is intended solely for
> the attention and use of the named addressee(s) and may be confidential or
> proprietary in nature or covered by the provisions of privacy act
> (Legislative Decree June, 30 2003, no.196 - Italy's New Data Protection
> Code).Any use not in accord with its purpose, any disclosure, reproduction,
> copying, distribution, or either dissemination, either whole or partial, is
> strictly forbidden except previous formal approval of the named
> addressee(s). If you are not the intended recipient, please contact
> immediately the sender by telephone, fax or e-mail and delete the
> information in this message that has been received in error. The sender
> does not give any warranty or accept liability as the content, accuracy or
> completeness of sent messages and accepts no responsibility for changes
> made after they were sent or for other risks which arise as a result of
> e-mail transmission, viruses, etc.
>
> -------------------------------------------------------
>
------------------------------------------------------------------------------
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the
conversation now. http://goparallel.sourceforge.net/
_______________________________________________
Geoserver-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-users
