Hello group!
i am using geoserver 2.8.3 on Tomcat 7.0.42 with this JVM:
java version "1.7.0_99"
OpenJDK Runtime Environment (IcedTea 2.6.5) (suse-24.33.2-x86_64)
OpenJDK 64-Bit Server VM (build 24.95-b01, mixed mode)
What i did: I was playing around with the postgis rasterdata tutorial.
While im
Sorry about that, didn't know why the response was only to you.
Hehe i'll search on google then, I asked because maybe there was some hidden
example in th geoserver docs.
Something I don't understand, you say that the exception is because the 16 bit
tiff. But why the layer preview fails when us
Dear Jose,
please, stay on the ML.
This can get you started :)
https://www.google.it/webhp?sourceid=chrome-instant&ion=1&espv=2&ie=UTF-8#q=geoserver%20rastersymbolizer
Regards,
Simone Giannecchini
==
GeoServer Professional Services from the experts!
Visit http://goo.gl/it488V for more informati
Ciao Jose,
short answer, your data is 16 bits hence they contains numbers about a
geophysical quantity ( maybe a DEM?) not colors.
Rendering in GeoServer happens in 8 bits, the functionality you are
trying to use is valid for RGB(A) or Gray(A) or Paletted imagery, all
in 8 bits per band.
You sho
Sorry, I forgot to say that also tried using a mosaic dataset pointing to a
directory where four of this scenes resides (only one band of this scenes). And
in that case i got this exception.
org.geoserver.platform.ServiceException: Error rendering coverage on the fast
path
at
org.geos
Hi,
I was using geoserver 2.8.2 with geotools 14.2 and when trying to set an
InputTransparentColor to a layer, an exception was thrown. The exception is:
org.geoserver.platform.ServiceException: Error rendering coverage on the fast
path
at
org.geoserver.wms.map.RenderedImageMapOutpu
Hello group!
i am using geoserver 2.8.3 on Tomcat 7.0.42 with this JVM:
java version "1.7.0_99"
OpenJDK Runtime Environment (IcedTea 2.6.5) (suse-24.33.2-x86_64)
OpenJDK 64-Bit Server VM (build 24.95-b01, mixed mode)
What i did: I was playing around with the postgis rasterdata tutorial.
While im
Hi,
We have just put that setting into the YAML as follows:
connectionTimeout: 9
socketTimeout: 18
brokenUrlPlaceholder: default
The result was that it still completes in around 30 seconds but with missing
layers and the following error message:
2016-04-19 17:07:58,309 ERROR [print.PDF
Hi Paul, I had a quick look at the code and it seems that you are right:
those settings are ignored.
I don't know if they were supported in 1.2 and deprecated in 2.x.
A patch to the library would be needed to (re)implement them.
Regards,
Mauro Bartolomeoli
2016-04-19 18:14 GMT+02:00 Paul Wittle
Hi Paul,
we use MapFish 2.1 in GeoServer 2.6 and above. The option you need for read
timeouts is probably socketTimeout. Did you try with that one?
Regards,
Mauro Bartolomeoli
2016-04-19 15:44 GMT+02:00 Paul Wittle :
> Hi,
>
>
>
> Is the GeoServer printing plugin using MapFish version 1.2 in Ge
Hi,
Is the GeoServer printing plugin using MapFish version 1.2 in GeoServer version
2.6 and above because I can't find how to get it to increase the read time for
big layers.
When reading aerial photography the MapFish component is logging a Read Time
Out error after 30 seconds even if I set t
Hi Nhan,
I think you could do this with a "group by NAME" in an SQL View -
http://docs.geoserver.org/stable/en/user/data/database/sqlview.html - at that
point each Name will only appear once as far as the layer is concerned.
Cheers,
jonathan
On Tue, 19 Apr 2016 14:15:49 +0100 Nhan Vo
Hi,
Assuming I have a feature /Person /with a /name /attribute, and in
PostGIS store I have:
Person 1: name=Ann
Person 2: name=Ann
Person 3: name=Ann
Person 4: name=Ba
Person 5: name=Bo
Person 6: name=Clech
Then with the following pseudo WFS GetFeature Url
/
//http://example.com/geoserver/wfs
Good to hear that it's solved for you, and that we have a work around :-)
Cheers
Andrea
On Tue, Apr 19, 2016 at 11:42 AM, matteo rivola
wrote:
> Hi,
>
> I have appended in every "datastore.properties" files for stored mosaics
> the string TypeNames=false, like suggested in
> https://osgeo-org.a
Hi,
I have appended in every "datastore.properties" files for stored mosaics
the string TypeNames=false, like suggested in
https://osgeo-org.atlassian.net/browse/GEOS-7500
After this change geoserver takes 106029 ms for startup instead of four and
a half hours.
It seems that the fix solved the p
Ok Andrea,
I will try with the suggested fix and I give you a response.
Thank you very much.
Cheers
2016-04-19 10:55 GMT+02:00 Andrea Aime :
> Hi Matteo,
> please keep the user list in CC :-)
> More comments inline
>
> On Tue, Apr 19, 2016 at 10:51 AM, matteo rivola
> wrote:
>
>> Hi Andrea,
>>
Hi Matteo,
please keep the user list in CC :-)
More comments inline
On Tue, Apr 19, 2016 at 10:51 AM, matteo rivola
wrote:
> Hi Andrea,
>
> I think the ticket linked above reports exactly my problem.
>
> Infact if DB tables for mosaics grow up, geoserver take more time for
> checking them.
>
>
Hi Matteo,
this one could be caused by https://osgeo-org.atlassian.net/browse/GEOS-7500
Can you check the ticket and verify if that matches your case?
Cheers
Andrea
On Tue, Apr 19, 2016 at 9:27 AM, matteo rivola wrote:
> Hi all,
>
> I'm using GeoServer 2.8.8, with JVM version 1.7.0_95 (OpenJD
Hi
I am just wondering if there is a way to programmatically delete a tile layer's
cache if the data from the layer is updated?
Currently looking at trying to create a script that will just delete the cache
from a scheduled task so I can make sure that the data is as current as
possible (withi
Hi all,
I'm using GeoServer 2.8.8, with JVM version 1.7.0_95 (OpenJDK 64-Bit Server
VM). I'm also using Postgresql server version 9.4.0, with a JNDI connection
Pool.
The problem is that when I start geoserver with about 700 ImageMosaic
stores already uploaded I see a time of about 20 seconds to l
20 matches
Mail list logo