Hi Jody,
I agree that we need a recalculation option.
>From our side, we are interested on implementing the proposal for coverages
but we don't have availability to do it on the short term (meaning that we
might work on it on the last quarter of the year or the 1Q of 2017, but I
can't warrant
This proposal came up in today's geosever meeting (
https://github.com/geoserver/geoserver/wiki/GSIP-140) - were you interested
in perusing this topic?
In addition to calculating during import (as proposed) we should allow
"info" to be recalculated via the REST API. This same limitation is
Hi Simone,
I have prepared a first draft for the proposal:
https://github.com/geoserver/geoserver/wiki/GSIP-140
It is not too concrete regarding implementation, but I think it correctly
outlines our requirement and how it would fit on the existing Geoserver
infrastructure.
Note that I have also
Ciao Cesar,
the existing processes do not store aything.
They can be used as a block-box/building block to compute what's
needed and then use separate code to store it in the config.
Regards,
Simone Giannecchini
==
GeoServer Professional Services from the experts!
Visit http://goo.gl/it488V for
Hi Simone, is the WPS process just calculating the stats, or is it also
storing the results on the coverage?
If it is doing both things, then it already covers our use case.
If not, it would be worthy indeed to handle it as an asynch import, using
the WPS process to get the results and storing
Dear Cesar,
please, find my comments inline below...
Regards,
Simone Giannecchini
==
GeoServer Professional Services from the experts!
Visit http://goo.gl/it488V for more information.
==
Ing. Simone Giannecchini
@simogeo
Founder/Director
GeoSolutions S.A.S.
Via di Montramito 3/A
55054 Massarosa
Dear Andrea,
On 10 February 2016 at 18:22, Andrea Aime
wrote:
> [SNIP]
> Does GeoTiff have statistics built in? First time I hear about it?
> Or are you talking about the GDAL statistics file (a xml file normally),
> which is not part of any standard?
> Indeed the
Dear Simone, I agree on creating a proposal to mature the exact scope and
the best way to implement it on Geoserver.
Some first ideas:
- WHAT:
1) Read raster statistics (max & mean) if available on the raster data
source
2) Compute min and max and store it on the CoverageDimension range (it
On Tue, Feb 9, 2016 at 6:21 PM, César Martínez Izquierdo <
cesar@gmail.com> wrote:
> We are interested on improving the behaviour of Geoserver regarding the
> management of raster statistics, which currently seems to be broken in
> several senses:
>
> a) It is not possible to update raster
Dear Cesar,
adding to Andrea's, your proposal is certainly interesting and we would be
glad to devote some our time helping out with this.
I would suggest to start with putting together a proposal that we can start
discussing on.
Regards,
Simone Giannecchini
==
GeoServer Professional Services
10 matches
Mail list logo