On 11 August 2016 at 07:16, Casper Børgesen (CABO) <c...@niras.dk> wrote:
> Hi Ian and Jukka
>
>
>
> @Ian
>
> That is a workaround that would work, but it is a lot of
> retiling/overviewing combined with returning the result 100% transparent
> just to make the getMap request fast.
>
You need that optimisation to get any sort of speed out of the getinfo
request too - otherwise GeoServer is reading in 100s+GB to return one point
each and every time.
I think you may be better off looking at WCS or WPS as better ways of doing
this.
Ian
------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity
planning reports. http://sdm.link/zohodev2dev
_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users
