On 01/06/16 00:26, Daniele Romagnoli wrote:
> On Tue, May 31, 2016 at 4:25 AM, Ben Caradoc-Davies
> wrote:
>> In a nutshell: should elevation variables that are *internal* to each
>> granule be indexed? Is this supported? If so, is indexer configuration
>> required? Why would
Hi Ivan,
We've had a project dig into the ImageMosaic plugin recently.
What happens if you use the GeoServer UI to re-'save' the ImageMosaic
layer? I've seen that reload just the datastores and layers associated.
If that doesn't work for the plugin, there may be a small bit of work
Hi,
wondering, which version of GeoServer are you using? I don't think we have
automatic tests
for materialized views so they might not work, but looking at the code, I
would suspect that
they might only work if one is using a recent version of GeoServer (e.g., a
2.8.x or later).
I would try out
That's what I wanted to, at first, but the query is really to heavy to
be on-the-fly via GeoServer. So I have to create this materialized view
on postgis (8min execution time !!) to build a new layer... maybe this
should be a new table ?
Le 31/05/2016 à 18:06, Blome, Guido (62-24) a écrit :
Hi Ivan,
I`m using materialized Views in Geoserver by building an SQL-View.
You just have to paste the SELECT Statement in the form behind the link
"configure SQL View" and it works. But your right they don't appear in the
normal Featuretype list.
But with the described workaround it works.
Hello all,
I have some issues with my connection PostGIS - GeoServer, when it comes
to Postgis views. I have created many *MATERIALIZED VIEW* with geometry
or geography fields. These fields can be found in the geometry_ or
geography_columns views, with the correct projection data.
When I'm
Hello All,
This might be quite trivial but I cannot seem to be able to figure it out
based on the Rest API documentation.
I have several ImageMosaic stores (each of them has exactly 1 layer) which
are in turn backed by GeoTIFF data files. Every few hours I refresh the
data by uploading new
W dniu 31.05.2016 o 14:20, Simone Giannecchini pisze:
> I agree with Andrea,
> please, open a JIRA report, we'll fix it right away.
https://osgeo-org.atlassian.net/browse/GEOS-7565
Maciej
--
What NetFlow Analyzer can
Hi Ben,
On Tue, May 31, 2016 at 4:25 AM, Ben Caradoc-Davies
wrote:
> Daniele,
>
> these dimensions are in effect a Z dimension. The data is sourced from
> GRIB2 but by the time it is ingested by ImageMosaic, it is equivalent to
> NetCDF (CDM API). Below I have included a
I agree with Andrea,
please, open a JIRA report, we'll fix it right away.
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
Hello all,
Since I couldn't find the sollution in previous posts with the same problem,
I need to present my problem with Geoserver here. Anyway, I installed
Geonetwork 2.10.4 and in installation process I checked installation of
Geoserver too. Geonetwork works fine, but when I try to go on
W dniu 31.05.2016 o 12:35, Andrea Aime pisze:
> So to be sure, it's a warning but the UI works anyways?
Yes, at least for reading.
Maciej
--
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
On Tue, May 31, 2016 at 12:24 PM, Maciej Filocha
wrote:
> After upgrading Geoserver to 2.9.0, I see the following warning in logs
> every time I open a "Cluster settings" tab:
>
> WARN [form.AbstractTextComponent] - Couldn't resolve model type of
>
>
After upgrading Geoserver to 2.9.0, I see the following warning in logs
every time I open a "Cluster settings" tab:
WARN [form.AbstractTextComponent] - Couldn't resolve model type of
Hi Jody et al.
Thank you for your outstanding work. I was eager to try the custom
legend image for a style but I'm not able to make it work. I'm using a
clean 2.9.0 war deployment on Tomcat 8.0.30.
This is what I did:
1. Add a new style, let's name it "another_raster" and generate a raster
Hi, I got the same error
Caused by: java.lang.IllegalArgumentException
.
.
Caused by: java.lang.RuntimeException: Unable to obtain connection: Cannot
create PoolableConnectionFactory (Exception opening port H2 TCP Server
(tcp://localhost:59575) (port may be in use), cause: timeout [90061-119])
16 matches
Mail list logo