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 statistics using REST API (see
message [1] on mailing list)
b) Geoserver apparently fails to (or doesn't make any effort to) read
raster statistics even if they are present of the raster data source (at
least for GeoTiff)
c) Geoserver apparently is not able to compute raster statistics from the
data source
We intend to correct a) in the sort term (meaning: now), but we might also
be interested on b) and c) on the long term depending on the required
effort.
For c), I envisage a parameter on REST requests for coverages which forces
the (re)calculation of statistics. For instance:
POST /workspaces/<ws>/coveragestores/<cs>/coverages[.<format>]?stats=yes
(when uploading the coverage)
GET /workspaces/<ws>/coveragestores/<cs>/coverages/<c>[.<format>]?stats=yes
(for an already published coverage)
Do you think it could be a good approach?
Best regards,
César
[1]
https://www.mail-archive.com/geoserver-users@lists.sourceforge.net/msg24434.html
--
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
César Martínez Izquierdo
GIS developer
- - - - - - - - - - - - - - - - - - - -
SCOLAB: http://www.scolab.es
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
