+1 - agreed that this seems like the "simplest" way forward.
On Thu, Nov 19, 2015 at 10:08 AM, cheesybiscuits
wrote:
> Wow, that is a long thread!
>
> I read / skimmed through the full conversation and what I take from it is
> there are numerous ways this could be
Wow, that is a long thread!
I read / skimmed through the full conversation and what I take from it is
there are numerous ways this could be done that would increase complexity,
deviate from GeoServer's UI philosophy, and consume lots of developer time,
but that Andrea's original suggestion - to
Actually after some more thought I think this situation is slightly
different (although the technical solution might end up being the same).
Here's the two cases as I understand them:
1) In my original case the need was to run a query against an Oracle
spatial table and return a geometry value
I've created a function within Oracle for on-the-fly clustering that I hoped
to query via GeoServer using an SQL view layer.
The function takes as its arguments the bounding box and the number of grid
cells to use in a basic gridded clustering process (i.e. find the centre of
mass for points
I think this is the same issue discussed in this (lengthy) thread:
http://osgeo-org.1560.x6.nabble.com/Reducing-query-data-size-in-Oracle-td5192620.html
TLDR: not possible right now, apparently requires clever development to
make it work.
If there has been improvement on this front it would be
Hi Martin,
it certainly looks similar, most likely same.
No new development, still not possible, people still welcome to chip in
with resources/funds:
https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer
Cheers
Andrea
On