On Thu, Mar 12, 2015 at 12:18 AM, Martin Davis <mtncl...@gmail.com> wrote:
> 1. allow specifying a SQL transformation expression to be invoked only
>>> when the query is being made for WMS rendering
>>>
>>
>> What I proposed previously (the bbox thing) has no WMS specific
>> limitations, and should still allow you to get what you want.
>>
>
> Hmmm.... not sure how this would support rendering transformed geometries,
> but get the raw data when needed via a WFS or GetFeatureInfo query?
>
Oh ok, so you _want_ to make it WMS specific... which confirms that I
should not have tried to answer this thread, I'm following
presentations at FOSS4G-NA and I don't have enough focus to follow this
thread the way I should... at the same time, if I don't try,
I would have to delay any answer by two weeks (when I will be back home in
a sane environment to think, instead of jet
lagged and at a conference at the same time)
>
> Or is this is supported by (a) adding an extra transformed geometry column
> (say GEOM_TRANS) to the SQL View query and then referring to that column in
> the SLD <Geometry> element? If so then that seems like a good solution.
>
Yes, this would be an approach... the downside is that your extra column
would also show up in WFS.
>
> It would also be nice to be able to alter the transformation based on the
> scale of the current query (as is done in the built-in simplify
> functionality, via the distance value). This might need some extra
> built-in parameters being exposed for use in the SQLView query.
>
Uuuh... the result might become very confusing... in the simple case you
might want to just change a function call,
in the complex one you might have to rewrite half of the query.
For something like that I'd use a different approach:
* create N sql views, one for each different data processing
* attach a different style with scale dependencies to each of them
* make them non advertised, and create a layer group hiding their structure
The WFS/GetFeatureInfo case would be handled by the one layer that is not
transformed, which you probably would advertise as normal
(and remember to query for GetFeatureInfo in place of the group).
Another completely different angle could be to go fully SLD driven, have
geometry transformations in SLD, and
make it so that we encode the functions in sql equivalents (if the db has
them)... but to go there, we'd first
have to implement support for expressions in Query selection (as opposed to
just listing properties), something
that Jody has been pushing for, but that I believe has no funding yet...
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
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users
