Hi,
If simplification on Oracle side starts to interest someday, this ticket follows what is going on in QGIS:
https://hub.qgis.org/issues/12298
-Jukka Rahkonen-
Andrea Aime wrote:
···
On Tue, Mar 10, 2015 at 11:07 PM, Martin Davis <mtnclimb@…84…> wrote:
Not sure I get all the constraints around this 100%, but generally the idea sounds good. I like the idea of being able to take control of the filter condition SQL being used (which pretty much requires access to the $bbox parameter). And it’s a good idea to make it optional, so it isn’t always executed.
Just to be clear, the %BOX%{and ST_Intersects(g.geom,$bbox)} syntax would be added to the SQLView SQL text?
Yep
Is the $bbox variable already available?
No, it would be something new that we replace only withing the context of a %BOX%{…} thing (aside, not really in love with the syntax,
any suggestion to make it look better? or just can just say that you like it)
Would an alternative be to use the same kind of syntax to specify the actual geometry column to use in the bbox filter? That would be less general, but also less error-prone.
No, that would require geoserver to understand the sql, and know where to add the filter, as said, would like to avoid going there.
You know your sql, you place the optional box filter in the suitable position, with the suitable syntax.
For the point from x, y case we might also want to provide minx,miny,maxx,maxy… actually, just providing these
could also be the way to go, if you want to build an envelope you have the spatial db syntax to do so.
Just thinking out loud.
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://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.