from:"Sabine Ohlendorf"

Re: [Geoserver-users] Imagemosaic: Input Transparent Color for 32bit tifs

2016-11-16 Thread Sabine Ohlendorf

Dear Simone,
as proposed I created a JIRA Issue for improvement on this topic:
https://osgeo-org.atlassian.net/browse/GEOS-7856

Regards,
Sabine

> Gesendet: Mittwoch, 09. November 2016 um 16:19 Uhr
> Von: "Simone Giannecchini" <simone.giannecch...@geo-solutions.it>
> An: "Sabine Ohlendorf" <sabine.ohlend...@gmx.de>
> Cc: "Simone Giannecchini" <simone.giannecch...@geo-solutions.it>, "Geoserver 
> Mailinglist" <geoserver-users@lists.sourceforge.net>
> Betreff: Re: Re: [Geoserver-users] Imagemosaic: Input Transparent Color for 
> 32bit tifs
>
> Ciao Sabine,
> open a jira report and attach some small sample data or a link to
> dropbox or something like that which we can use.
> 
> We might give you an ftp server privately if needed.
> 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 (LU)
> Italy
> phone: +39 0584 962313
> fax: +39 0584 1660272
> mob:   +39  333 8128928
> 
> http://www.geo-solutions.it
> http://twitter.com/geosolutions_it
> 
> ---
> AVVERTENZE AI SENSI DEL D.Lgs. 196/2003
> Le informazioni contenute in questo messaggio di posta elettronica e/o
> nel/i file/s allegato/i sono da considerarsi strettamente riservate.
> Il loro utilizzo è consentito esclusivamente al destinatario del
> messaggio, per le finalità indicate nel messaggio stesso. Qualora
> riceviate questo messaggio senza esserne il destinatario, Vi preghiamo
> cortesemente di darcene notizia via e-mail e di procedere alla
> distruzione del messaggio stesso, cancellandolo dal Vostro sistema.
> Conservare il messaggio stesso, divulgarlo anche in parte,
> distribuirlo ad altri soggetti, copiarlo, od utilizzarlo per finalità
> diverse, costituisce comportamento contrario ai principi dettati dal
> D.Lgs. 196/2003.
> 
> The information in this message and/or attachments, is intended solely
> for the attention and use of the named addressee(s) and may be
> confidential or proprietary in nature or covered by the provisions of
> privacy act (Legislative Decree June, 30 2003, no.196 - Italy's New
> Data Protection Code).Any use not in accord with its purpose, any
> disclosure, reproduction, copying, distribution, or either
> dissemination, either whole or partial, is strictly forbidden except
> previous formal approval of the named addressee(s). If you are not the
> intended recipient, please contact immediately the sender by
> telephone, fax or e-mail and delete the information in this message
> that has been received in error. The sender does not give any warranty
> or accept liability as the content, accuracy or completeness of sent
> messages and accepts no responsibility  for changes made after they
> were sent or for other risks which arise as a result of e-mail
> transmission, viruses, etc.
> 
> 
> On Wed, Nov 9, 2016 at 1:59 PM, Sabine Ohlendorf
> <sabine.ohlend...@gmx.de> wrote:
> > Hi Simone,
> >
> > thank you for your message and sorry for late reply.
> > I will try to update to the new version of geoserver (2.8.x) and test.
> >
> > How could I provide some sample data to you?
> > Regards,
> > Sabine
> >
> >
> >> Gesendet: Dienstag, 25. Oktober 2016 um 09:13 Uhr
> >> Von: "Simone Giannecchini" <simone.giannecch...@geo-solutions.it>
> >> An: "Sabine Ohlendorf" <sabine.ohlend...@gmx.de>
> >> Cc: "Geoserver Mailinglist" <geoserver-users@lists.sourceforge.net>
> >> Betreff: Re: [Geoserver-users] Imagemosaic: Input Transparent Color for 
> >> 32bit tifs
> >>
> >> Ciao Sabine,
> >> as you noticed the XXXTransparentColor settings do not apply to "real"
> >> data (float, double, 16bits etc...).
> >>
> >> Wit the latest versions of GeoServer (2.8.x and on if my memory serves
> >> me right) if you enable JAI-Ext there should be proper support for
> >> nodata introduced, hence you simply have to make sure your data
> >> reports nodata properly.
> >>
> >> Maybe some sample data could help identifying this issue.
> >>
> >> Regards,
> >> Simone Giannecchini
> >> ==
> >> GeoServer Professional Services from the experts!
> >> Visit http://goo.gl/it488V for more information.
> >> ==
> >> Ing. Simone Giannecchini
> >> @simogeo
> >> Founder/Director
>

Re: [Geoserver-users] Imagemosaic: Input Transparent Color for 32bit tifs

2016-11-09 Thread Sabine Ohlendorf

Hi Simone,

thank you for your message and sorry for late reply.
I will try to update to the new version of geoserver (2.8.x) and test.

How could I provide some sample data to you? 
Regards,
Sabine


> Gesendet: Dienstag, 25. Oktober 2016 um 09:13 Uhr
> Von: "Simone Giannecchini" <simone.giannecch...@geo-solutions.it>
> An: "Sabine Ohlendorf" <sabine.ohlend...@gmx.de>
> Cc: "Geoserver Mailinglist" <geoserver-users@lists.sourceforge.net>
> Betreff: Re: [Geoserver-users] Imagemosaic: Input Transparent Color for 32bit 
> tifs
>
> Ciao Sabine,
> as you noticed the XXXTransparentColor settings do not apply to "real"
> data (float, double, 16bits etc...).
> 
> Wit the latest versions of GeoServer (2.8.x and on if my memory serves
> me right) if you enable JAI-Ext there should be proper support for
> nodata introduced, hence you simply have to make sure your data
> reports nodata properly.
> 
> Maybe some sample data could help identifying this issue.
> 
> 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 (LU)
> Italy
> phone: +39 0584 962313
> fax: +39 0584 1660272
> mob:   +39  333 8128928
> 
> http://www.geo-solutions.it
> http://twitter.com/geosolutions_it
> 
> ---
> AVVERTENZE AI SENSI DEL D.Lgs. 196/2003
> Le informazioni contenute in questo messaggio di posta elettronica e/o
> nel/i file/s allegato/i sono da considerarsi strettamente riservate.
> Il loro utilizzo è consentito esclusivamente al destinatario del
> messaggio, per le finalità indicate nel messaggio stesso. Qualora
> riceviate questo messaggio senza esserne il destinatario, Vi preghiamo
> cortesemente di darcene notizia via e-mail e di procedere alla
> distruzione del messaggio stesso, cancellandolo dal Vostro sistema.
> Conservare il messaggio stesso, divulgarlo anche in parte,
> distribuirlo ad altri soggetti, copiarlo, od utilizzarlo per finalità
> diverse, costituisce comportamento contrario ai principi dettati dal
> D.Lgs. 196/2003.
> 
> The information in this message and/or attachments, is intended solely
> for the attention and use of the named addressee(s) and may be
> confidential or proprietary in nature or covered by the provisions of
> privacy act (Legislative Decree June, 30 2003, no.196 - Italy's New
> Data Protection Code).Any use not in accord with its purpose, any
> disclosure, reproduction, copying, distribution, or either
> dissemination, either whole or partial, is strictly forbidden except
> previous formal approval of the named addressee(s). If you are not the
> intended recipient, please contact immediately the sender by
> telephone, fax or e-mail and delete the information in this message
> that has been received in error. The sender does not give any warranty
> or accept liability as the content, accuracy or completeness of sent
> messages and accepts no responsibility  for changes made after they
> were sent or for other risks which arise as a result of e-mail
> transmission, viruses, etc.
> 
> 
> On Mon, Oct 24, 2016 at 6:14 PM, Sabine Ohlendorf
> <sabine.ohlend...@gmx.de> wrote:
> > Dear List,
> >
> > I am using Geoserver 2.7.5. I want to create a layer out of several 
> > geotiffs so I created an imagemosaic. The geotiffs are 32bit tifs an I want 
> > to colorize them using Geoserver Styles. The single tifs overlap at the 
> > edges and partly have no data values there which appear in the mosaic. To 
> > avoid that I wanted to set the "Input Transparent Color". But when setting 
> > a value I get an Error:
> >
> > org.geotools.data.DataSourceException: Unable to create this mosaic
> > at 
> > org.geotools.gce.imagemosaic.RasterLayerResponse.prepareResponse(RasterLayerResponse.java:1336)
> > at 
> > org.geotools.gce.imagemosaic.RasterLayerResponse.processRequest(RasterLayerResponse.java:1226)
> > at 
> > org.geotools.gce.imagemosaic.RasterLayerResponse.createResponse(RasterLayerResponse.java:1192)
> > at 
> > org.geotools.gce.imagemosaic.RasterManager.read(RasterManager.java:1153)
> > at 
> > org.geotools.gce.imagemosaic.ImageMosaicReader.read(ImageMosaicReader.java:874)
> > at 
> > org.geotools.gce.imagemosaic.ImageMosaicReader.read(ImageMosaicReader.java:853)
> > at 
> > org.geoserver.catalog.SingleGridCoverage2DReader.read(SingleGridCoverage2DR

Re: [Geoserver-users] RESP API add CoverageStore

2016-11-09 Thread Sabine Ohlendorf

Hi David,

I recommend to test your REST commands with curl before building into your C+ 
program. See http://docs.geoserver.org/stable/en/user/rest/examples/curl.html

For creating a coverageStore you have to send the raster data directly. You 
don't have to send any xml code.

Here is an example for creating a geotiff coveragestore with curl:
curl -v -u : -XPUT -H "Content-type:application/zip" 
--data-binary @ 
http:///geoserver/rest/workspaces//coveragestores//file.geotiff

You have to send the data as zip file and use -XPUT if you send it to a remote 
server. 

IF your data is already located on the server where geoserver is running you 
can use (curl example):
curl -v -u : -XPOST -H "Content-type:text/plain"
 -d "file:///" 
http:///geoserver/rest/workspaces//coveragestores//external.geotiff

See also http://docs.geoserver.org/stable/en/user/rest/api/coveragestores.html

Hope I could help.

Kind regards,
Sabine


> Gesendet: Dienstag, 08. November 2016 um 09:21 Uhr
> Von: "David Alda Fernandez de Lezea" 
> An: "GeoServer Users" 
> Betreff: [Geoserver-users] RESP API add CoverageStore
>
> Hi list,
> 
> I'm trying to add a coverage store through REST API but I'm not sure if it's 
> possible or if I'm doing it the right way. Here's my scenario:
> 
> I've got several ECW raster files that I want to automatically be populated 
> using the REST API. So far I've achieved to populate a workspace, buy when it 
> comes to add a CoverageStore I get a 405 Method not permitted response. I'm 
> sending the requests from a C# program using normal WebRequests. I've 
> configured DIGEST Auth following 
> http://docs.geoserver.org/latest/en/user/security/tutorials/digest/index.html 
> 
> Now, here's the data I'm sending:
> 
> PRUEBAnew_workspace_csharp_2truefile://\\192.168.1.15\\IMAGENES_SATELITE\\SENTINEL2\\S2A_OPER_MSI_L1C_DS_EPA_20150821T111616945Z_IrRG.ecwECW
> 
> I've tried sending the method as PUT and POST but without success in both 
> cases.
> 
> So my questions are:
> 
> Is it possible to add a Covergae Store from the REST API?
> 
> Is ECW format supported for REST API - Coverage Store?
> 
> When sending the request, the url should be something like 
> http://mygeoserver.com/rest/TELEDETEKZIOA/coveragestores/S2A_OPER_MSI_L1C_DS_EPA_20150821T111616945Z_IrRG.ecw
>   ???
> 
> Any ideas why I'm getting a 405 response?
> 
> Thanks in advance. 
> 
> Regards,
> 
> Agur bero bat,
> 
> 
> David Alda Fernández de Lezea
> Área de Sistemas de Información Geográfica, Planificación Territorial y 
> Forestal Informazio Geografikoen Sistemak, Lurralde eta Baso Antolaketaren 
> Arloa.
> da...@hazi.eus | www.hazi.eus
> T 945 003 240 - M 627 923 170 - F 945 003 290 
> Hazi | Granja Modelo de Arkaute s/n | 01192 Arkaute - Araba
>  
> *  LEGE OHARRA   ***   AVISOLEGAL   
> ***   DISCLAIMER   *
> Mezu hau pertsonala eta isilpekoa da eta baimenik gabeko erabilera debekatua 
> dago legalki. Jasotzailea ez bazara ezabatu mezua, bidali eta kontserbatu 
> gabe.
> Este mensaje es personal y confidencial y su uso no autorizado está prohibido 
> legalmente. Si usted no es el destinatario, proceda a borrarlo, sin 
> reenviarlo ni conservarlo.
> This message is personal and confidential, unauthorised use is legally 
> prohibited. If you are not the intended recipient, delete it without 
> resending or backing it.
> 
> 
> 
> --
> Developer Access Program for Intel Xeon Phi Processors
> Access to Intel Xeon Phi processor-based developer platforms.
> With one year of Intel Parallel Studio XE.
> Training and support from Colfax.
> Order your platform today. http://sdm.link/xeonphi
> ___
> Geoserver-users mailing list
> Geoserver-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geoserver-users
>

--
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today. http://sdm.link/xeonphi
___
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

[Geoserver-users] Imagemosaic: Input Transparent Color for 32bit tifs

2016-10-24 Thread Sabine Ohlendorf

Dear List,

I am using Geoserver 2.7.5. I want to create a layer out of several geotiffs so 
I created an imagemosaic. The geotiffs are 32bit tifs an I want to colorize 
them using Geoserver Styles. The single tifs overlap at the edges and partly 
have no data values there which appear in the mosaic. To avoid that I wanted to 
set the "Input Transparent Color". But when setting a value I get an Error:

org.geotools.data.DataSourceException: Unable to create this mosaic
at 
org.geotools.gce.imagemosaic.RasterLayerResponse.prepareResponse(RasterLayerResponse.java:1336)
at 
org.geotools.gce.imagemosaic.RasterLayerResponse.processRequest(RasterLayerResponse.java:1226)
at 
org.geotools.gce.imagemosaic.RasterLayerResponse.createResponse(RasterLayerResponse.java:1192)
at 
org.geotools.gce.imagemosaic.RasterManager.read(RasterManager.java:1153)
at 
org.geotools.gce.imagemosaic.ImageMosaicReader.read(ImageMosaicReader.java:874)
at 
org.geotools.gce.imagemosaic.ImageMosaicReader.read(ImageMosaicReader.java:853)
at 
org.geoserver.catalog.SingleGridCoverage2DReader.read(SingleGridCoverage2DReader.java:147)
at 
org.geoserver.catalog.CoverageDimensionCustomizerReader.read(CoverageDimensionCustomizerReader.java:227)
at 
org.geoserver.catalog.CoverageDimensionCustomizerReader.read(CoverageDimensionCustomizerReader.java:217)
at 
org.geoserver.wms.featureinfo.RasterLayerIdentifier.identify(RasterLayerIdentifier.java:170)
at org.geoserver.wms.GetFeatureInfo.execute(GetFeatureInfo.java:78)
at org.geoserver.wms.GetFeatureInfo.run(GetFeatureInfo.java:44)
... 107 more
Caused by: java.lang.IllegalStateException: Unsupported data type.
at 
org.geotools.image.ImageWorker.makeColorTransparent(ImageWorker.java:1848)
at 
org.geotools.gce.imagemosaic.RasterLayerResponse.createBlankResponse(RasterLayerResponse.java:1675)
at 
org.geotools.gce.imagemosaic.RasterLayerResponse.prepareResponse(RasterLayerResponse.java:1333)
... 118 more

It seems it is not possible to set the InputTransparentColor for 32bit images 
which seems logical. But how can I get a similar setting for 32bit images?

Regards,
Sabine

--
Check out the vibrant tech community on one of the world's most 
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
___
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Re: [Geoserver-users] Problem changing bounding box of imagemosaic layer

2016-10-12 Thread Sabine Ohlendorf

Hi Jason,

thanks for your hint. Untfortunately it is not the solution of the problem. I checked the indexer.properties file, caching is already set to false.

Sabine

Gesendet: Freitag, 30. September 2016 um 14:44 Uhr
Von: "Jason Newmoyer" <ja...@newmoyergeospatial.com>
An: "P O'Toole" <p.oto...@uwyo.edu>
Cc: "Sabine Ohlendorf" <sabine.ohlend...@gmx.de>, "geoserver-users@lists.sourceforge.net" <geoserver-users@lists.sourceforge.net>
Betreff: Re: [Geoserver-users] Problem changing bounding box of imagemosaic layer

I remember having a similar issue that I worked through. Now I can ingest tiles in real time and see updates immediately to the layer. 

I believe it was this setting in the indexer.properties file:

# (Optional) A boolean flag to disable/enable caching. When enabled the ImageMosaic will try to pin in memory the entire content of the index to reduce loading/query time. If we have a large granule index and/or we want to ingest in real time new granules (e.g. the index is on a database and we interact directly with it) we need to disable caching, otherwise we can enable it.

Caching=false

Jason Newmoyer
Newmoyer Geospatial Solutions
843.606.0424
ja...@newmoyergeospatial.com

On Thu, Sep 29, 2016 at 3:00 PM, P O'Toole <p.oto...@uwyo.edu> wrote:

Sabine –

Hm. I may be wrong, but this sounds like a bug. You might consider filing a report.

If you update the underlying data frequently in the work that you do and can't wait on a bugfix, I would try to determine what else forces an update, such as clearing Geoserver's cache for the layer, etc ( potentially relevant: http://gis.stackexchange.com/questions/77240/ ) . (Obviously, you've found that deleting/recreating the layer does the trick.) From there, you may just automate this, and arrange to clone/delete/remake/empty the cache for the layer using Geoserver's configuration REST API, and have this happen either periodically or whenever you make edits from your database.

- Patrick

-Original Message-
From: Sabine Ohlendorf [mailto:sabine.ohlend...@gmx.de]
Sent: Thursday, September 29, 2016 2:07 AM
To: P O'Toole <p.oto...@uwyo.edu>
Cc: geoserver-users@lists.sourceforge.net
Subject: Aw: Re: Problem changing bounding box of imagemosaic layer

Hi Patrick,
I also tried viewing the data via an OpenLayers web application (not only Geoservers prewiew) and the data is still clipped to the old bounding box.
Sabine

>
> Have you tried viewing the data in QGIS or OpenLayers before and after changing the bounding box? Are data being clipped to the old bounding box still or is it simply Geoserver's preview that's going stale when you chance the bbox?
>
> - Patrick O'Toole
>
--
___
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

--
Check out the vibrant tech community on one of the world's most 
engaging tech sites, SlashDot.org! http://sdm.link/slashdot___
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Re: [Geoserver-users] OutOfMemoryError: Java heap space

2016-09-30 Thread Sabine Ohlendorf


Thanks Andrea!

The request logging filter solved the problem! I now just disabled the logging of full bodies and kept general request logging filter enabled. Would you recommend to also disable the general request logging filter?

 

Regards,
Sabine

 

Gesendet: Donnerstag, 29. September 2016 um 12:37 Uhr
Von: "Andrea Aime" <andrea.a...@geo-solutions.it>
An: "Sabine Ohlendorf" <sabine.ohlend...@gmx.de>
Cc: "geoserver-userslists.sourceforge.net" <geoserver-users@lists.sourceforge.net>
Betreff: Re: [Geoserver-users] OutOfMemoryError: Java heap space


Sabine, it seems you have the request logging filter enabled and logging fully bodies (see web.xml)... disable it if you want to make large uploads,
or provide a patch to set a limit to how much gets logged (the logging filter is considered a debugging tool, not to be used

for production, that's why it does not have a built-in limit, but one could be added)

 

Cheers

Andrea

 


 
On Thu, Sep 29, 2016 at 10:17 AM, Sabine Ohlendorf <sabine.ohlend...@gmx.de> wrote:

Dear List,

I am using Geoserver 2.7.5 and I am using REST Api for creating datastores and layers.
Now I have the problem that Geoserver throws a java.lang.OutOfMemoryError:
Exception in thread "ajp-bio-9018-exec-5" java.lang.OutOfMemoryError: Java heap space
        at java.util.Arrays.copyOf(Arrays.java:2367)
        at java.lang.AbstractStringBuilder.expandCapacity(AbstractStringBuilder.java:130)
        at java.lang.AbstractStringBuilder.ensureCapacityInternal(AbstractStringBuilder.java:114)
        at java.lang.AbstractStringBuilder.append(AbstractStringBuilder.java:415)
        at java.lang.StringBuffer.append(StringBuffer.java:237)
        at org.apache.log4j.helpers.PatternParser$LiteralPatternConverter.format(PatternParser.java:420)
        at org.apache.log4j.PatternLayout.format(PatternLayout.java:503)
        at org.apache.log4j.WriterAppender.subAppend(WriterAppender.java:301)
        at org.apache.log4j.WriterAppender.append(WriterAppender.java:159)
        at org.apache.log4j.AppenderSkeleton.doAppend(AppenderSkeleton.java:230)
        at org.apache.log4j.helpers.AppenderAttachableImpl.appendLoopOnAppenders(AppenderAttachableImpl.java:65)
        at org.apache.log4j.Category.callAppenders(Category.java:203)
        at org.apache.log4j.Category.forcedLog(Category.java:388)
        at org.apache.log4j.Category.info(Category.java:663)
        at org.geotools.util.logging.Log4JLogger.info(Log4JLogger.java:135)
        at org.geoserver.filters.LoggingFilter.doFilter(LoggingFilter.java:81)
        at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
        at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
        at org.geoserver.filters.GZIPFilter.doFilter(GZIPFilter.java:42)
        at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
        at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
        at org.geoserver.filters.SessionDebugFilter.doFilter(SessionDebugFilter.java:48)
        at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
        at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
        at org.geoserver.filters.FlushSafeFilter.doFilter(FlushSafeFilter.java:44)
        at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
        at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
        at org.vfny.geoserver.filters.SetCharacterEncodingFilter.doFilter(SetCharacterEncodingFilter.java:109)
        at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
        at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
        at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:220)
        at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:122)

First I thought that the image that I wanted to upload was too big, approx 260MB. But I could upload a much bigger image (700MB) without problems.
I read a lot within the list but could not find a solution. As described in http://docs.geoserver.org/latest/en/user/production/troubleshooting.html I printed the heap status via jmap but to be honest I cannot read anything out of it:

Attaching to process ID 2023, please wait...
Debugger attached successfully.
Server compiler detected.
JVM version is 24.75-b04

using thread-local object allocation.
Parallel GC with 1 thread(s)

Heap Configuration:
   MinHeapFreeRatio = 0
   MaxHeapFreeRatio = 100
   MaxHeapSize      = 3288334336 (3136.0MB)
   NewSize          = 1310720 (1.25MB)
   MaxNewSize       = 17592186044415 MB

Re: [Geoserver-users] OutOfMemoryError: Java heap space

2016-09-30 Thread Sabine Ohlendorf



Hi Alberto,
 

Thanks for your reply! I played a bit with the parameter but in the end disabling of the request logging filter solved the problem. But thanks for reminding me to keep an eye on these parameters!

Regards, Sabine


 

Gesendet: Donnerstag, 29. September 2016 um 11:56 Uhr
Von: "Alberto Callejas Delgado" <alberto.calle...@deimos-space.com>
An: "Sabine Ohlendorf" <sabine.ohlend...@gmx.de>
Cc: "geoserver-userslists.sourceforge.net" <geoserver-users@lists.sourceforge.net>
Betreff: Re: [Geoserver-users] OutOfMemoryError: Java heap space


Hello Sabine,
 

The reference values for the parameters applied for optimizing JVM in tomcat (based on some research) are below but obviously this is not a rule of thumb:

 

HEAP="-Xms2048m -Xmx2048m"

NEW="-XX:NewSize=128m -XX:MaxNewSize=128m"

RMIGC="-Dsun.rmi.dgc.client.gcInterval=60 -

Dsun.rmi.dgc.server.gcInterval=60"

PGC="-XX:+UseParallelGC"

PERM="-XX:PermSize=128m -XX:MaxPermSize=128m"

DEBUG="-verbose:gc -XX:+PrintTenuringDistribution"

DUMP="-XX:+HeapDumpOnOutOfMemoryError"

SERVER="-server" 

 

Try to investigate a bit more about each parameter and try to find the best solution for your needs.

 

I would say the parallel garbage collector (Parallel GC) with 1 thread might be to low.

 

Best,

 

Alberto


 
 






--
___
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

[Geoserver-users] OutOfMemoryError: Java heap space

2016-09-29 Thread Sabine Ohlendorf

Dear List,

I am using Geoserver 2.7.5 and I am using REST Api for creating datastores and 
layers.
Now I have the problem that Geoserver throws a java.lang.OutOfMemoryError:
Exception in thread "ajp-bio-9018-exec-5" java.lang.OutOfMemoryError: Java heap 
space
at java.util.Arrays.copyOf(Arrays.java:2367)
at 
java.lang.AbstractStringBuilder.expandCapacity(AbstractStringBuilder.java:130)
at 
java.lang.AbstractStringBuilder.ensureCapacityInternal(AbstractStringBuilder.java:114)
at 
java.lang.AbstractStringBuilder.append(AbstractStringBuilder.java:415)
at java.lang.StringBuffer.append(StringBuffer.java:237)
at 
org.apache.log4j.helpers.PatternParser$LiteralPatternConverter.format(PatternParser.java:420)
at org.apache.log4j.PatternLayout.format(PatternLayout.java:503)
at org.apache.log4j.WriterAppender.subAppend(WriterAppender.java:301)
at org.apache.log4j.WriterAppender.append(WriterAppender.java:159)
at org.apache.log4j.AppenderSkeleton.doAppend(AppenderSkeleton.java:230)
at 
org.apache.log4j.helpers.AppenderAttachableImpl.appendLoopOnAppenders(AppenderAttachableImpl.java:65)
at org.apache.log4j.Category.callAppenders(Category.java:203)
at org.apache.log4j.Category.forcedLog(Category.java:388)
at org.apache.log4j.Category.info(Category.java:663)
at org.geotools.util.logging.Log4JLogger.info(Log4JLogger.java:135)
at org.geoserver.filters.LoggingFilter.doFilter(LoggingFilter.java:81)
at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
at org.geoserver.filters.GZIPFilter.doFilter(GZIPFilter.java:42)
at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
at 
org.geoserver.filters.SessionDebugFilter.doFilter(SessionDebugFilter.java:48)
at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
at 
org.geoserver.filters.FlushSafeFilter.doFilter(FlushSafeFilter.java:44)
at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
at 
org.vfny.geoserver.filters.SetCharacterEncodingFilter.doFilter(SetCharacterEncodingFilter.java:109)
at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
at 
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:220)
at 
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:122)

First I thought that the image that I wanted to upload was too big, approx 
260MB. But I could upload a much bigger image (700MB) without problems.
I read a lot within the list but could not find a solution. As described in 
http://docs.geoserver.org/latest/en/user/production/troubleshooting.html I 
printed the heap status via jmap but to be honest I cannot read anything out of 
it:

Attaching to process ID 2023, please wait...
Debugger attached successfully.
Server compiler detected.
JVM version is 24.75-b04

using thread-local object allocation.
Parallel GC with 1 thread(s)

Heap Configuration:
   MinHeapFreeRatio = 0
   MaxHeapFreeRatio = 100
   MaxHeapSize  = 3288334336 (3136.0MB)
   NewSize  = 1310720 (1.25MB)
   MaxNewSize   = 17592186044415 MB
   OldSize  = 5439488 (5.1875MB)
   NewRatio = 2
   SurvivorRatio= 8
   PermSize = 21757952 (20.75MB)
   MaxPermSize  = 268435456 (256.0MB)
   G1HeapRegionSize = 0 (0.0MB)

Heap Usage:
PS Young Generation
Eden Space:
   capacity = 522190848 (498.0MB)
   used = 35361864 (33.72370147705078MB)
   free = 486828984 (464.2762985229492MB)
   6.77182760583349% used
>From Space:
   capacity = 287309824 (274.0MB)
   used = 0 (0.0MB)
   free = 287309824 (274.0MB)
   0.0% used
To Space:
   capacity = 286785536 (273.5MB)
   used = 0 (0.0MB)
   free = 286785536 (273.5MB)
   0.0% used
PS Old Generation
   capacity = 2192572416 (2091.0MB)
   used = 1492816408 (1423.6606674194336MB)
   free = 699756008 (667.3393325805664MB)
   68.08515865229238% used
PS Perm Generation
   capacity = 106954752 (102.0MB)
   used = 88507512 (84.40734100341797MB)
   free = 18447240 (17.59265899658203MB)
   82.75229510139016% used

36895 interned Strings occupying 3920704 bytes.

Can anybody help?
Thanks!
Regards, Sabine

Re: [Geoserver-users] Problem changing bounding box of imagemosaic layer

2016-09-29 Thread Sabine Ohlendorf

Hi Patrick,
I also tried viewing the data via an OpenLayers web application (not only 
Geoservers prewiew) and the data is still clipped to the old bounding box.
Sabine



> 
> Have you tried viewing the data in QGIS or OpenLayers before and after 
> changing the bounding box? Are data being clipped to the old bounding box 
> still or is it simply Geoserver's preview that's going stale when you chance 
> the bbox?
> 
> - Patrick O'Toole
> 

--
___
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Re: [Geoserver-users] Problem changing bounding box of imagemosaic layer

2016-09-27 Thread Sabine Ohlendorf

Hi,

anyone an idea? Again I faced the problem that I cannot enlarge the bounding 
box when I add data. Actually I can enlarge the boundingbox via the 
administration interface but geoserver still only shows the original bounding 
box.
I there any other place where the boundingbox is set? 

Regards,
Sabine Ohlendorf



-
Dear mailing list,

I am using a Geoserver Version 2.7.5.
I have an imagemosaic layer of a coverage based on postgis database. I use this 
layer for timeseries raster data. The boundingbox for the layer was set to an 
AOI. I now ingested additional data to this layer which covered a bigger area 
which is why I changed the boundingsbox of the layer to a bigger one. So I 
enlarged the boundingbox via the administration web interface.
But within in the layer preview it still showed the old smaller boundingbox. 
When I clicked on "Compute from data" for the boundingbox it changed back to 
the smaller boundingbox although the data I added to the layer/coverage covered 
a bigger area. So how can I change the boundingbox to a bigger area?

I ended up deleting the coverage and recreate it. But this is probably not the 
intended way doing it. Can anybody help?

Thanks!
Regards,
Sabine 

--
___
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

[Geoserver-users] Problem changing bounding box of imagemosaic layer

2016-08-16 Thread Sabine Ohlendorf

Dear mailing list,

I am using a Geoserver Version 2.7.5. 
I have an imagemosaic layer of a coverage based on postgis database. I use this 
layer for timeseries raster data. The boundingbox for the layer was set to an 
AOI. I now ingested additional data to this layer which covered a bigger area 
which is why I changed the boundingsbox of the layer to a bigger one. So I 
enlarged the boundingbox via the administration web interface.
But within in the layer preview it still showed the old smaller boundingbox. 
When I clicked on "Compute from data" for the boundingbox it changed back to 
the smaller boundingbox although the data I added to the layer/coverage covered 
a bigger area. So how can I change the boundingbox to a bigger area?

I ended up deleting the coverage and recreate it. But this is probably not the 
intended way doing it. Can anybody help?

Thanks!
Regards,
Sabine


--
___
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

[Geoserver-users] Geoserver layer security with AOI and time

2016-02-12 Thread Sabine Ohlendorf

Dear list,

I looked through the archive but didn't find suitable information.
I have a GeoServer 2.7.1.1 running and would like to extend security settings. 
I read about the "Layer Security" in the GeoServer User Manual which is already 
a very good feature. But I am wondering if it is also possible to restrict 
access
 * to certain AOI for example via a defined polygon
 * to certain time interval (as I have layers with time parameter)

One thing I found in the web is to install a proxy server like 'mapproxy' to 
handle this kind of requirements.
Does somebody has experience with this topic and can give some recommendation?

Thanks,
Sabine Ohlendorf


--
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=/4140
___
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Re: [Geoserver-users] Geoserver layer security with AOI and time

2016-02-12 Thread Sabine Ohlendorf

Thanks for the fast reply!

I forgot to mention that I would like to have the restricted access (certain AOI and certain time interval) for WMS requests. Does the geofence plugin cover this?

Cheers,

Sabine

Gesendet: Freitag, 12. Februar 2016 um 12:07 Uhr
Von: "Andrea Aime" <andrea.a...@geo-solutions.it>
An: "Sabine Ohlendorf" <sabine.ohlend...@gmx.de>
Cc: "Geoserver Mailinglist" <geoserver-users@lists.sourceforge.net>
Betreff: Re: [Geoserver-users] Geoserver layer security with AOI and time

On Fri, Feb 12, 2016 at 11:57 AM, Sabine Ohlendorf <sabine.ohlend...@gmx.de> wrote:

Dear list,

I looked through the archive but didn't find suitable information.
I have a GeoServer 2.7.1.1 running and would like to extend security settings. I read about the "Layer Security" in the GeoServer User Manual which is already a very good feature. But I am wondering if it is also possible to restrict access
* to certain AOI for example via a defined polygon
* to certain time interval (as I have layers with time parameter)

I would suggest to try the GeoFence plugin, it can setup both types of filter. The second it won't be an explicit dimension filter, but

you can setup a CQL filter that will have the same effect on most layer (probably not on stand alone NetCDF layers,

but if it's a vector layer, or an image mosaic, it should work.

Cheers

Andrea

GeoServer Professional Services from the experts! Visit

http://goo.gl/it488V for more information.

Ing. Andrea Aime

@geowolf

Technical Lead

GeoSolutions S.A.S.
Via di Montramito 3/A
55054 Massarosa (LU)

phone: +39 0584 962313

fax: +39 0584 1660272

mob: +39 339 8844549

http://www.geo-solutions.it

http://twitter.com/geosolutions_it

AVVERTENZE AI SENSI DEL D.Lgs. 196/2003

Le informazioni contenute in questo messaggio di posta elettronica e/o nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il loro utilizzo è consentito esclusivamente al destinatario del messaggio, per le finalità indicate nel messaggio stesso. Qualora riceviate questo messaggio senza esserne il destinatario, Vi preghiamo cortesemente di darcene notizia via e-mail e di procedere alla distruzione del messaggio stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso, divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od utilizzarlo per finalità diverse, costituisce comportamento contrario ai principi dettati dal D.Lgs. 196/2003.

The information in this message and/or attachments, is intended solely for the attention and use of the named addressee(s) and may be confidential or proprietary in nature or covered by the provisions of privacy act (Legislative Decree June, 30 2003, no.196 - Italy's New Data Protection Code).Any use not in accord with its purpose, any disclosure, reproduction, copying, distribution, or either dissemination, either whole or partial, is strictly forbidden except previous formal approval of the named addressee(s). If you are not the intended recipient, please contact immediately the sender by telephone, fax or e-mail and delete the information in this message that has been received in error. The sender does not give any warranty or accept liability as the content, accuracy or completeness of sent messages and accepts no responsibility for changes made after they were sent or for other risks which arise as a result of e-mail transmission, viruses, etc.

---

--
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=/4140___
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Re: [Geoserver-users] Problems with REST on some coveragestores

2015-06-02 Thread Sabine Ohlendorf

Hi,

by chance I found the solution of the problem myself:
I found out that I was trying to ingest 32bit tif data to a layer with datatype 
64bits. That was the reason why it didn't accept the data.

Still it is strange that this didn't throw an error or appeared in any logfile. 
It would have been good to receive an Error as answer on the REST request.

Regards,
Sabine

--
___
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Re: [Geoserver-users] Problems with REST on some coveragestores

2015-06-01 Thread Sabine Ohlendorf

Hi,

@Eric:thanks for the hint. We are already working with a jndi datasource.

@Andrea: good to know :)

Cheers,

Sabine

Gesendet:Montag, 01. Juni 2015 um 13:58 Uhr
Von:Andrea Aime andrea.a...@geo-solutions.it
An:Eric Smets eric.sm...@fks.be
Cc:Sabine Ohlendorf sabine.ohlend...@gmx.de, Geoserver Mailinglist geoserver-users@lists.sourceforge.net
Betreff:Re: [Geoserver-users] Problems with REST on some coveragestores

On Mon, Jun 1, 2015 at 12:31 PM, Eric Smets eric.sm...@fks.be wrote:

Hello,

The issue comes probably from the open connections to your database.

If you have a standard postgres/postgis installation the number of simultanous connection has limits.

You can augment this limit but, if the flow introduces always new coverages then soon or later this will happen again.

The best solution is to work with a jndi datasource defined in your tomcat/jetty container and use this connection in

the geoserver definition.

By the way, the issue of leaking connections in mosaics backed by jdbc stores should be solved in 2.7.1,

and in 2.6.x nightly builds too

Cheers

Andrea

GeoServer Professional Services from the experts! Visit

http://goo.gl/it488V for more information.

Ing. Andrea Aime

@geowolf

Technical Lead

GeoSolutions S.A.S.

Via Poggio alle Viti 1187

55054 Massarosa (LU)

Italy

phone: +39 0584 962313

fax: +39 0584 1660272

mob: +39 339 8844549

http://www.geo-solutions.it

http://twitter.com/geosolutions_it

AVVERTENZE AI SENSI DEL D.Lgs. 196/2003

Le informazioni contenute in questo messaggio di posta elettronica e/o nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il loro utilizzo consentito esclusivamente al destinatario del messaggio, per le finalit indicate nel messaggio stesso. Qualora riceviate questo messaggio senza esserne il destinatario, Vi preghiamo cortesemente di darcene notizia via e-mail e di procedere alla distruzione del messaggio stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso, divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od utilizzarlo per finalit diverse, costituisce comportamento contrario ai principi dettati dal D.Lgs. 196/2003.

The information in this message and/or attachments, is intended solely for the attention and use of the named addressee(s) and may be confidential or proprietary in nature or covered by the provisions of privacy act (Legislative Decree June, 30 2003, no.196 - Italys New Data Protection Code).Any use not in accord with its purpose, any disclosure, reproduction, copying, distribution, or either dissemination, either whole or partial, is strictly forbidden except previous formal approval of the named addressee(s). If you are not the intended recipient, please contact immediately the sender by telephone, fax or e-mail and delete the information in this message that has been received in error. The sender does not give any warranty or accept liability as the content, accuracy or completeness of sent messages and accepts no responsibility for changes made after they were sent or for other risks which arise as a result of e-mail transmission, viruses, etc.

---

--
___
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

[Geoserver-users] Problems with REST on some coveragestores

2015-06-01 Thread Sabine Ohlendorf

Hi,

I have a geoserver version 2.7.0 running on Ubuntu 14.4. and I am using the REST interface to create new coveragestores and layers or to add further data to an existing coveragestore. In general this is working quite good.

I have some python scripts sending the REST requests to the server, via python package requests. But since a few days I have problems ingesting new data to some of my coveragestores. For other coveragestores everything is still working without problems. I am always using the same requests.

POST-Reqeust to the URL:

http://ipaddress/geoserver/rest/workspaces/my-workspace/coveragestores/my-coveragestore/file.imagemosaic

A zip file with one tif image is sent.

I also tried the corresponding request via curl:

curl -v -u username:password -XPOST -H Content-type:application/zip --data-binary @path-to-zip http://ipaddress/geoserver/rest/workspaces/my-workspace/coveragestores/my-coveragestore/file.imagemosaic

The result is the same. The data is not included into the coveragestore. But I dont get any error message. The HTTP return code is 202 - Accepted and the tif file is copied to the geoserver to the correct data directory of the coveragestore but it is not included into the coveragestore. We are using a database with the following database.properties file for the coveragestores:

# JNDI specific #
SPI=org.geotools.data.postgis.PostgisNGJNDIDataStoreFactory
jndiReferenceName=jdbc/postgres

Loose bbox=true

preparedStatements=false

Looking through the log files of geoserver and postgresql I could not find any error message.

/var/lib/tomcat/geoserver_master/logs/catalina.out

/var/lib/tomcat/geoserver_master/logs/localhost_access_log.2015-06-01.txt

/var/log/postgresql/postgresql-9.3-main.log

Everything looks normal. But the image is not ingested to the coveragestore. The strange thing is that for some coveragestores it is still working and for others I have these problem which just occured from one day to the other.

Does anyone has an idea? Are the maybe some more logfiles I could check?

Thanks.

Sabine

--
___
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Re: [Geoserver-users] Imagemosaic with SLD not fully displayed

2015-02-23 Thread Sabine Ohlendorf

HI,



I created a JIRA on the JIRA page for GeoServer last week: GEOS-6892

Link: https://jira.codehaus.org/browse/GEOS-6892



Unfortunately there are no answers so far.

Sabine

--
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration  more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=190641631iu=/4140/ostg.clktrk___
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Re: [Geoserver-users] Imagemosaic with SLD not fully displayed

2015-02-12 Thread Sabine Ohlendorf

,

Sabine



Gesendet:Donnerstag, 12. Februar 2015 um 10:04 Uhr
Von:Daniele Romagnoli daniele.romagn...@geo-solutions.it
An:Sabine Ohlendorf sabine.ohlend...@gmx.de
Cc:Geoserver Mailinglist geoserver-users@lists.sourceforge.net
Betreff:Re: [Geoserver-users] Imagemosaic with SLD not fully displayed







Hi Sabine,
do you have any chance to share a minimal set of data to replicate the issue for debugging?
Side questions:
- Can you run a gdalinfo on one of your samples and provide us the output?
- Can you also provide us the coverage configuration? (the coverage.xml. You can find it in the GEOSERVER_DATA_DIR/workspaces/yourworkspace/yourcoveragestore/yourcoverage/coverage.xml)

Please, let us know.
Best Regards,
Daniele










==
GeoServer Professional Services from the experts! Visit
http://goo.gl/NWWaa2 for more information.
==

Ing. Daniele Romagnoli
Senior Software Engineer

GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272

http://www.geo-solutions.it
http://twitter.com/geosolutions_it

---
AVVERTENZE AI SENSI DEL D.Lgs. 196/2003

Le informazioni contenute in questo messaggio di posta elettronica e/o nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il loro utilizzo  consentito esclusivamente al destinatario del messaggio, per le finalit indicate nel messaggio stesso. Qualora riceviate questo messaggio senza esserne il destinatario, Vi preghiamo cortesemente di darcene notizia via e-mail e di procedere alla distruzione del messaggio stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso, divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od utilizzarlo per finalit diverse, costituisce comportamento contrario ai principi dettati dal D.Lgs. 196/2003.



The information in this message and/or attachments, is intended solely for the attention and use of the named addressee(s) and may be confidential or proprietary in nature or covered by the provisions of privacy act (Legislative Decree June, 30 2003, no.196 - Italys New Data Protection Code).Any use not in accord with its purpose, any disclosure, reproduction, copying, distribution, or either dissemination, either whole or partial, is strictly forbidden except previous formal approval of the named addressee(s). If you are not the intended recipient, please contact immediately the sender by telephone, fax or e-mail and delete the information in this message that has been received in error. The sender does not give any warranty or accept liability as the content, accuracy or completeness of sent messages and accepts no responsibility for changes made after they were sent or for other risks which arise as a result of e-mail transmission, viruses, etc.









On Wed, Feb 11, 2015 at 2:16 PM, Sabine Ohlendorf sabine.ohlend...@gmx.de wrote:




Hi all,

I am using geoserver 2.6.1 and have a problem with SLDs:
I created a new style as SLD (see below). Furthermore I have an imagemosaic layer with 32bit geotiffs where I put the created style as default style in the WMS settings.
When I start the OpenLayers LayerPreview the style is used in general but the problem is that values smaller 1 within the image are not displayed at first. It is necessary to zoom in until a scale of 1:150K. Then the values are displayed in the appropriate colors of the style.

Before I used geoserver 2.2.5 with the same setting and the same style and it was workling without problems.

Kinrd regards,

Sabine


SLD:



?xml version=1.0 encoding=UTF-8?
sld:StyledLayerDescriptor xmlns:ogc=http://www.opengis.net/ogc xmlns:xlink=http://www.w3.org/1999/xlink xmlns:sld=http://www.opengis.net/sld xmlns:gml=http://www.opengis.net/gml xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance version=1.0.0 xsi:schemaLocation=http://www.opengis.net/sld http://schemas.opengis.net/sld/1.0.0/StyledLayerDescriptor.xsd
sld:NamedLayer xmlns=http://www.opengis.net/sldsld:Name4db8e899a3a245588c282af02e849433/sld:Name
sld:UserStylesld:NameStyle1/sld:Name
sld:TitleWater Mask/sld:Title
sld:Abstract/
sld:FeatureTypeStylesld:NameTurbidity/sld:Name
sld:TitleTurbidity/sld:Title
sld:Abstract;/sld:Abstract
sld:SemanticTypeIdentifiergeneric:geometry/sld:SemanticTypeIdentifier
sld:Rulesld:NameWater Mask - /sld:Name
sld:TitleWater Mask - /sld:Title
sld:RasterSymbolizersld:ColorMap
sld:ColorMapEntry color=#808080 quantity=-6 opacity=0.0 label=/
sld:ColorMapEntry color=#808080 quantity=-5 opacity=0.0 label=/
sld:ColorMapEntry color=#808080 quantity=-4 opacity=0.0 label=/
sld:ColorMapEntry color=#808080 quantity=-3 opacity=0.0 label=/
sld:ColorMapEntry color=#808080 quantity=-2 opacity=0.0 label=/
sld:ColorMapEntry color=#808080 quantity=-1 opacity=0.0 label=/
sld:ColorMapEntry color=#808080 quantity=0 opacity=0.0 label=/
sld:ColorMapEntry color=#190019 quantity=0.001 opacity=1.0 label=/
sld:ColorMapEntry color=#190019 quantity=0.1 opacity=1.0 label

[Geoserver-users] Imagemosaic with SLD not fully displayed

2015-02-11 Thread Sabine Ohlendorf

Hi all,

I am using geoserver 2.6.1 and have a problem with SLDs:
I created a new style as SLD (see below). Furthermore I have an imagemosaic layer with 32bit geotiffs where I put the created style as default style in the WMS settings.
When I start the OpenLayers LayerPreview the style is used in general but the problem is that values smaller 1 within the image are not displayed at first. It is necessary to zoom in until a scale of 1:150K. Then the values are displayed in the appropriate colors of the style.

Before I used geoserver 2.2.5 with the same setting and the same style and it was workling without problems.

Kinrd regards,

Sabine


SLD:



?xml version=1.0 encoding=UTF-8?
sld:StyledLayerDescriptor xmlns:ogc=http://www.opengis.net/ogc xmlns:xlink=http://www.w3.org/1999/xlink xmlns:sld=http://www.opengis.net/sld xmlns:gml=http://www.opengis.net/gml xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance version=1.0.0 xsi:schemaLocation=http://www.opengis.net/sld http://schemas.opengis.net/sld/1.0.0/StyledLayerDescriptor.xsd
sld:NamedLayer xmlns=http://www.opengis.net/sldsld:Name4db8e899a3a245588c282af02e849433/sld:Name
sld:UserStylesld:NameStyle1/sld:Name
sld:TitleWater Mask/sld:Title
sld:Abstract/
sld:FeatureTypeStylesld:NameTurbidity/sld:Name
sld:TitleTurbidity/sld:Title
sld:Abstract;/sld:Abstract
sld:SemanticTypeIdentifiergeneric:geometry/sld:SemanticTypeIdentifier
sld:Rulesld:NameWater Mask - /sld:Name
sld:TitleWater Mask - /sld:Title
sld:RasterSymbolizersld:ColorMap
sld:ColorMapEntry color=#808080 quantity=-6 opacity=0.0 label=/
sld:ColorMapEntry color=#808080 quantity=-5 opacity=0.0 label=/
sld:ColorMapEntry color=#808080 quantity=-4 opacity=0.0 label=/
sld:ColorMapEntry color=#808080 quantity=-3 opacity=0.0 label=/
sld:ColorMapEntry color=#808080 quantity=-2 opacity=0.0 label=/
sld:ColorMapEntry color=#808080 quantity=-1 opacity=0.0 label=/
sld:ColorMapEntry color=#808080 quantity=0 opacity=0.0 label=/
sld:ColorMapEntry color=#190019 quantity=0.001 opacity=1.0 label=/
sld:ColorMapEntry color=#190019 quantity=0.1 opacity=1.0 label=/
sld:ColorMapEntry color=#100059 quantity=0.124 opacity=1.0 label=/
sld:ColorMapEntry color=#0600A1 quantity=0.169 opacity=1.0 label=/
sld:ColorMapEntry color=#002ED2 quantity=0.229 opacity=1.0 label=/
sld:ColorMapEntry color=#0080E4 quantity=0.311 opacity=1.0 label=/
sld:ColorMapEntry color=#00B3EF quantity=0.423 opacity=1.0 label=/
sld:ColorMapEntry color=#00E6FA quantity=0.575 opacity=1.0 label=/
sld:ColorMapEntry color=#00F4CC quantity=0.782 opacity=1.0 label=/
sld:ColorMapEntry color=#00DE66 quantity=1.063 opacity=1.0 label=/
sld:ColorMapEntry color=#00C800 quantity=1.445 opacity=1.0 label=/
sld:ColorMapEntry color=#66DE00 quantity=1.965 opacity=1.0 label=/
sld:ColorMapEntry color=#CCF400 quantity=2.671 opacity=1.0 label=/
sld:ColorMapEntry color=#FFCC00 quantity=3.631 opacity=1.0 label=/
sld:ColorMapEntry color=#FF6600 quantity=4.936 opacity=1.0 label=/
sld:ColorMapEntry color=#FF quantity=6.709 opacity=1.0 label=/
sld:ColorMapEntry color=#CC0033 quantity=9.12 opacity=1.0 label=/
sld:ColorMapEntry color=#990066 quantity=12.397 opacity=1.0 label=/
sld:ColorMapEntry color=#990099 quantity=16.853 opacity=1.0 label=/
sld:ColorMapEntry color=#CC00CC quantity=22.909 opacity=1.0 label=/
sld:ColorMapEntry color=#FF00FF quantity=31.141 opacity=1.0 label=/
sld:ColorMapEntry color=#FF26FF quantity=42.332 opacity=1.0 label=/
sld:ColorMapEntry color=#FF49FF quantity=57.544 opacity=1.0 label=/
sld:ColorMapEntry color=#FF6AFF quantity=78.223 opacity=1.0 label=/
sld:ColorMapEntry color=#FF8EFF quantity=106.333 opacity=1.0 label=/
sld:ColorMapEntry color=#FFAFFF quantity=144.544 opacity=1.0 label=/

/sld:ColorMap
/sld:RasterSymbolizer
/sld:Rule
/sld:FeatureTypeStyle
/sld:UserStyle
/sld:NamedLayer
/sld:StyledLayerDescriptor





--
Dive into the World of Parallel Programming. The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net/___
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Re: [Geoserver-users] geoserver REST API imagemosaic

2015-01-22 Thread Sabine Ohlendorf

Hi Nicola,

thank you very much for your response. I managed to harvest a file as a zipfile
by using the file.imagemosaic extension. Great!

Just a comment for all who also want to harvest files to a GeoServer located on
another machine: It is necessary to use the @-sign within the curl command.
curl -v -u admin:geoserver -XPOST -H Content-type:application/zip
--data-binary @///path/to/the/zipfile/update.zip
http://IPaddress/geoserver/rest/workspaces/myworkspace/coveragestores/testmosaic/file.imagemosaic

Otherwise the zipfile is not fully uploaded which results in an error.

Regards,
Sabine

Gesendet: Mittwoch, 21. Januar 2015 um 14:00 Uhr
Von: Nicola Lagomarsini nicola.lagomars...@geo-solutions.it
An: Sabine Ohlendorf sabine.ohlend...@gmx.de
Cc: geoserver-users@lists.sourceforge.net
geoserver-users@lists.sourceforge.net
Betreff: Re: [Geoserver-users] geoserver REST API imagemosaic

Hi Sabine,
sorry for the delay. If you want to harvest a local file from to a GeoServer
located into another machine you can use two methods:

Mount a storage pointing to your local machine on the GeoServer machine and
harvest the file using the external.imagemosaic extension.
Zip the file to harvest and then harvest it using the file.imagemosaic
extension. You have to use the zip file because otherwise you can't mantain the
filename and this could be bad in cas of ImageMosaic with external dimensions.
Note that you have to set the Content-type to application/zip
Using the external.imagemosaic extension requires that the file is reachable
from the GeoServer machine; using file.imagemosaic instead allows to move
your files into the Store directory.
Hoping it could help.
Regards,
Nicola Lagomarsini.

--
New Year. New Location. New Benefits. New Data Center in Ashburn, VA.
GigeNET is offering a free month of service with a new server in Ashburn.
Choose from 2 high performing configs, both with 100TB of bandwidth.
Higher redundancy.Lower latency.Increased capacity.Completely compliant.
http://p.sf.net/sfu/gigenet
___
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

[Geoserver-users] geoserver REST API imagemosaic

2015-01-16 Thread Sabine Ohlendorf

Hi all,

I am using geoserver 2.6.1 and spent some time on getting used with the REST API. I basically followed REST examples for cURL from here:
http://docs.geoserver.org/stable/en/user/rest/examples/curl.html

I managed to define and configure a new image mosaic via
curl -u admin:geoserver -XPUT -H Content-type:application/zip --data-binary @testmosaic.zip http://IPaddress/geoserver/rest/workspaces/myworkspace/coveragestores/testmosaic/file.imagemosaic
The difference to the curl example from the geoserver docs is just the location of the geoserver. I run the curl command from my local machine. The geoserver is running on another machine within the local network. But everything worked fine.
But it another story when I want to harvest another file to an existing imagemosaic. The geoserver docs give the following command, which I adapted for my configuration:
curl -v -u admin:geoserver -XPOST -H Content-type: text/plain -d file:///path/to/the/file/newfile.tif http://IPaddress/geoserver/rest/workspaces/myworkspace/coveragestores/testmosaic/external.imagemosaic
Here I get an error that the file file:///path/to/the/file/newfile.tif was not found, when I run the command from my local machine with a file path on my local machine.

If I transfer the image file to the geoserver machine and run the command directly on the geoserver machine the file is harvested to the imagemosaic without problems.

My question: is there a possibility to harvest new files from my local machine to an existing imagemosaic when the geoserver is not running on the local machine but on another machine within the local network? Or is that procedure not intended?

Kind regards,
Sabine Ohlendorf

--
New Year. New Location. New Benefits. New Data Center in Ashburn, VA.
GigeNET is offering a free month of service with a new server in Ashburn.
Choose from 2 high performing configs, both with 100TB of bandwidth.
Higher redundancy.Lower latency.Increased capacity.Completely compliant.
http://p.sf.net/sfu/gigenet___
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Re: [Geoserver-users] Imagemosaic: Input Transparent Color for 32bit tifs

Re: [Geoserver-users] Imagemosaic: Input Transparent Color for 32bit tifs

Re: [Geoserver-users] RESP API add CoverageStore

[Geoserver-users] Imagemosaic: Input Transparent Color for 32bit tifs

Re: [Geoserver-users] Problem changing bounding box of imagemosaic layer

Re: [Geoserver-users] OutOfMemoryError: Java heap space

Re: [Geoserver-users] OutOfMemoryError: Java heap space

[Geoserver-users] OutOfMemoryError: Java heap space

Re: [Geoserver-users] Problem changing bounding box of imagemosaic layer

Re: [Geoserver-users] Problem changing bounding box of imagemosaic layer

[Geoserver-users] Problem changing bounding box of imagemosaic layer

[Geoserver-users] Geoserver layer security with AOI and time

Re: [Geoserver-users] Geoserver layer security with AOI and time

Re: [Geoserver-users] Problems with REST on some coveragestores

Re: [Geoserver-users] Problems with REST on some coveragestores

[Geoserver-users] Problems with REST on some coveragestores

Re: [Geoserver-users] Imagemosaic with SLD not fully displayed

Re: [Geoserver-users] Imagemosaic with SLD not fully displayed

[Geoserver-users] Imagemosaic with SLD not fully displayed

Re: [Geoserver-users] geoserver REST API imagemosaic

[Geoserver-users] geoserver REST API imagemosaic

21 matches

Site Navigation

Mail list logo

Footer information