[Geoserver-users] ImageMosaic problem when updating the store

Dear list,

I discovered a strange behavior using the ImageMosaic Plugin. I could successfully create the imagemosaic stores using the REST interface. But when extending the store with new data using the external.imagemosaic function, some mosaic stores were not updated.

I could identify some difference in the data: If I want to use data that are converted before with the gdal_translate -co NBITS=1 command, the geoserver throws an error: WARN [gce.imagemosaic] - Failure occurred while collecting the granules. See error message below. It works fine when I do not convert the data! The imagemosaic store creation works fine for both. Just updating is not possible when data are converted before.

The relevant gdalinfo differences are listed here (first file the not converted data, second file the NBITS=1 converted data):

< Band 1 Block=17393x1 Type=Byte, ColorInterp=Gray


Band 1 Block=17393x3 Type=Byte, ColorInterp=Palette

32a34,38

Image Structure Metadata:

NBITS=1

Color Table (RGB with 2 entries)

0: 0,0,0,255

1: 255,255,255,255

Is this a known problem or can you provide any quick solution for that?

Thanks,

Jonas

26 Apr 18:15:43 WARN [gce.imagemosaic] - Failure occurred while collecting the granules

org.apache.commons.io.DirectoryWalker$CancelException: Operation Cancelled

at org.apache.commons.io.DirectoryWalker.checkIfCancelled(DirectoryWalker.java:395)

at org.apache.commons.io.DirectoryWalker.walk(DirectoryWalker.java:368)

at org.apache.commons.io.DirectoryWalker.walk(DirectoryWalker.java:335)

at org.geotools.gce.imagemosaic.ImageMosaicDirectoryWalker$MosaicDirectoryWalker.(ImageMosaicDirectoryWalker.java:114)

at org.geotools.gce.imagemosaic.ImageMosaicDirectoryWalker.run(ImageMosaicDirectoryWalker.java:196)

at org.geotools.gce.imagemosaic.ImageMosaicReader$HarvestedResource.harvestCalculation(ImageMosaicReader.java:405)

at org.geotools.gce.imagemosaic.ImageMosaicReader$HarvestedResource.access$100(ImageMosaicReader.java:187)

at org.geotools.gce.imagemosaic.ImageMosaicReader$HarvestedResource$1.harvest(ImageMosaicReader.java:202)

at org.geotools.gce.imagemosaic.ImageMosaicReader.harvest(ImageMosaicReader.java:1250)

at org.geoserver.catalog.CoverageDimensionCustomizerReader$CoverageDimensionCustomizerStructuredReader.harvest(CoverageDimensionCustomizerReader.java:128)

at org.geoserver.catalog.rest.CoverageStoreFileResource.handlePost(CoverageStoreFileResource.java:90)

at org.restlet.Finder.handle(Finder.java:296)

at org.geoserver.rest.BeanDelegatingRestlet.handle(BeanDelegatingRestlet.java:38)

at org.restlet.Filter.doHandle(Filter.java:105)

at org.restlet.Filter.handle(Filter.java:134)

at org.restlet.Router.handle(Router.java:444)

at org.geoserver.rest.RESTDispatcher$1.handle(RESTDispatcher.java:205)

at com.noelios.restlet.ext.servlet.ServletConverter.service(ServletConverter.java:129)

at org.geoserver.rest.RESTDispatcher.handleRequestInternal(RESTDispatcher.java:87)

at org.springframework.web.servlet.mvc.AbstractController.handleRequest(AbstractController.java:153)

at org.springframework.web.servlet.mvc.SimpleControllerHandlerAdapter.handle(SimpleControllerHandlerAdapter.java:48)

at org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:923)

at org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:852)

at org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:882)

at org.springframework.web.servlet.FrameworkServlet.doPost(FrameworkServlet.java:789)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:648)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:729)

Dear Jonas,

I’m not sure to have fully understood your use case.

However, please note that ImageMosaic doesn’t allow to have granules with different sampleModel/colorModel within the same mosaic.

Therefore:
A) - If you are creating an ImageMosaic on a Gray dataset and then you are afterwards harvesting 1-bit paletted granules into the same mosaic, that update won’t work (by design).

B) - If you are creating an ImageMosaic on a paletted 1-bit dataset and then you are afterwards harvesting Gray Byte granules into the same mosaic, that update won’t work (by design).

C) - If you are creating an ImageMosaic on a paletted 1-bit dataset and then you are afterwards harvesting paletted 1-bit granules into the same mosaic, it should work.

D) - If you are creating an ImageMosaic on a gray dataset and then you are afterwards harvesting gray granules into the same mosaic, it should work.

If your case is one of A or B, then that it’s the expected behaviour.

If your case is one of C or D and it doesn’t work, then we should investigate on this. In that case you could open a JIRA with sample data to replicate the issue.

Please, let us know.

Hope this helps.

Cheers,

Daniele

···

On Sun, Apr 26, 2015 at 7:13 PM, Jonas Eberle <jonas.eberle@anonymised.com> wrote:

Dear list,

I discovered a strange behavior using the ImageMosaic Plugin. I could successfully create the imagemosaic stores using the REST interface. But when extending the store with new data using the external.imagemosaic function, some mosaic stores were not updated.

I could identify some difference in the data: If I want to use data that are converted before with the gdal_translate -co NBITS=1 command, the geoserver throws an error: WARN [gce.imagemosaic] - Failure occurred while collecting the granules. See error message below. It works fine when I do not convert the data! The imagemosaic store creation works fine for both. Just updating is not possible when data are converted before.

The relevant gdalinfo differences are listed here (first file the not converted data, second file the NBITS=1 converted data):

< Band 1 Block=17393x1 Type=Byte, ColorInterp=Gray


Band 1 Block=17393x3 Type=Byte, ColorInterp=Palette

32a34,38

Image Structure Metadata:

NBITS=1

Color Table (RGB with 2 entries)

0: 0,0,0,255

1: 255,255,255,255

Is this a known problem or can you provide any quick solution for that?

Thanks,

Jonas

26 Apr 18:15:43 WARN [gce.imagemosaic] - Failure occurred while collecting the granules

org.apache.commons.io.DirectoryWalker$CancelException: Operation Cancelled

at org.apache.commons.io.DirectoryWalker.checkIfCancelled(DirectoryWalker.java:395)

at org.apache.commons.io.DirectoryWalker.walk(DirectoryWalker.java:368)

at org.apache.commons.io.DirectoryWalker.walk(DirectoryWalker.java:335)

at org.geotools.gce.imagemosaic.ImageMosaicDirectoryWalker$MosaicDirectoryWalker.(ImageMosaicDirectoryWalker.java:114)

at org.geotools.gce.imagemosaic.ImageMosaicDirectoryWalker.run(ImageMosaicDirectoryWalker.java:196)

at org.geotools.gce.imagemosaic.ImageMosaicReader$HarvestedResource.harvestCalculation(ImageMosaicReader.java:405)

at org.geotools.gce.imagemosaic.ImageMosaicReader$HarvestedResource.access$100(ImageMosaicReader.java:187)

at org.geotools.gce.imagemosaic.ImageMosaicReader$HarvestedResource$1.harvest(ImageMosaicReader.java:202)

at org.geotools.gce.imagemosaic.ImageMosaicReader.harvest(ImageMosaicReader.java:1250)

at org.geoserver.catalog.CoverageDimensionCustomizerReader$CoverageDimensionCustomizerStructuredReader.harvest(CoverageDimensionCustomizerReader.java:128)

at org.geoserver.catalog.rest.CoverageStoreFileResource.handlePost(CoverageStoreFileResource.java:90)

at org.restlet.Finder.handle(Finder.java:296)

at org.geoserver.rest.BeanDelegatingRestlet.handle(BeanDelegatingRestlet.java:38)

at org.restlet.Filter.doHandle(Filter.java:105)

at org.restlet.Filter.handle(Filter.java:134)

at org.restlet.Router.handle(Router.java:444)

at org.geoserver.rest.RESTDispatcher$1.handle(RESTDispatcher.java:205)

at com.noelios.restlet.ext.servlet.ServletConverter.service(ServletConverter.java:129)

at org.geoserver.rest.RESTDispatcher.handleRequestInternal(RESTDispatcher.java:87)

at org.springframework.web.servlet.mvc.AbstractController.handleRequest(AbstractController.java:153)

at org.springframework.web.servlet.mvc.SimpleControllerHandlerAdapter.handle(SimpleControllerHandlerAdapter.java:48)

at org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:923)

at org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:852)

at org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:882)

at org.springframework.web.servlet.FrameworkServlet.doPost(FrameworkServlet.java:789)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:648)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:729)


One dashboard for servers and applications across Physical-Virtual-Cloud
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y


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

==
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 - 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.

Hi Daniele,

thanks for your response. Unfortunately C is the case. It works fine on gray datasets. I will open an issue with a sample dataset.

Cheers,
Jonas

···

----- Am 27. Apr 2015 um 12:17 schrieb Daniele Romagnoli daniele.romagnoli@anonymised.com:

Dear Jonas,

I’m not sure to have fully understood your use case.

However, please note that ImageMosaic doesn’t allow to have granules with different sampleModel/colorModel within the same mosaic.

Therefore:
A) - If you are creating an ImageMosaic on a Gray dataset and then you are afterwards harvesting 1-bit paletted granules into the same mosaic, that update won’t work (by design).

B) - If you are creating an ImageMosaic on a paletted 1-bit dataset and then you are afterwards harvesting Gray Byte granules into the same mosaic, that update won’t work (by design).

C) - If you are creating an ImageMosaic on a paletted 1-bit dataset and then you are afterwards harvesting paletted 1-bit granules into the same mosaic, it should work.

D) - If you are creating an ImageMosaic on a gray dataset and then you are afterwards harvesting gray granules into the same mosaic, it should work.

If your case is one of A or B, then that it’s the expected behaviour.

If your case is one of C or D and it doesn’t work, then we should investigate on this. In that case you could open a JIRA with sample data to replicate the issue.

Please, let us know.

Hope this helps.

Cheers,

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 - 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 Sun, Apr 26, 2015 at 7:13 PM, Jonas Eberle <jonas.eberle@anonymised.com> wrote:

Dear list,

I discovered a strange behavior using the ImageMosaic Plugin. I could successfully create the imagemosaic stores using the REST interface. But when extending the store with new data using the external.imagemosaic function, some mosaic stores were not updated.

I could identify some difference in the data: If I want to use data that are converted before with the gdal_translate -co NBITS=1 command, the geoserver throws an error: WARN [gce.imagemosaic] - Failure occurred while collecting the granules. See error message below. It works fine when I do not convert the data! The imagemosaic store creation works fine for both. Just updating is not possible when data are converted before.

The relevant gdalinfo differences are listed here (first file the not converted data, second file the NBITS=1 converted data):

< Band 1 Block=17393x1 Type=Byte, ColorInterp=Gray


Band 1 Block=17393x3 Type=Byte, ColorInterp=Palette

32a34,38

Image Structure Metadata:

NBITS=1

Color Table (RGB with 2 entries)

0: 0,0,0,255

1: 255,255,255,255

Is this a known problem or can you provide any quick solution for that?

Thanks,

Jonas

26 Apr 18:15:43 WARN [gce.imagemosaic] - Failure occurred while collecting the granules

org.apache.commons.io.DirectoryWalker$CancelException: Operation Cancelled

at org.apache.commons.io.DirectoryWalker.checkIfCancelled(DirectoryWalker.java:395)

at org.apache.commons.io.DirectoryWalker.walk(DirectoryWalker.java:368)

at org.apache.commons.io.DirectoryWalker.walk(DirectoryWalker.java:335)

at org.geotools.gce.imagemosaic.ImageMosaicDirectoryWalker$MosaicDirectoryWalker.(ImageMosaicDirectoryWalker.java:114)

at org.geotools.gce.imagemosaic.ImageMosaicDirectoryWalker.run(ImageMosaicDirectoryWalker.java:196)

at org.geotools.gce.imagemosaic.ImageMosaicReader$HarvestedResource.harvestCalculation(ImageMosaicReader.java:405)

at org.geotools.gce.imagemosaic.ImageMosaicReader$HarvestedResource.access$100(ImageMosaicReader.java:187)

at org.geotools.gce.imagemosaic.ImageMosaicReader$HarvestedResource$1.harvest(ImageMosaicReader.java:202)

at org.geotools.gce.imagemosaic.ImageMosaicReader.harvest(ImageMosaicReader.java:1250)

at org.geoserver.catalog.CoverageDimensionCustomizerReader$CoverageDimensionCustomizerStructuredReader.harvest(CoverageDimensionCustomizerReader.java:128)

at org.geoserver.catalog.rest.CoverageStoreFileResource.handlePost(CoverageStoreFileResource.java:90)

at org.restlet.Finder.handle(Finder.java:296)

at org.geoserver.rest.BeanDelegatingRestlet.handle(BeanDelegatingRestlet.java:38)

at org.restlet.Filter.doHandle(Filter.java:105)

at org.restlet.Filter.handle(Filter.java:134)

at org.restlet.Router.handle(Router.java:444)

at org.geoserver.rest.RESTDispatcher$1.handle(RESTDispatcher.java:205)

at com.noelios.restlet.ext.servlet.ServletConverter.service(ServletConverter.java:129)

at org.geoserver.rest.RESTDispatcher.handleRequestInternal(RESTDispatcher.java:87)

at org.springframework.web.servlet.mvc.AbstractController.handleRequest(AbstractController.java:153)

at org.springframework.web.servlet.mvc.SimpleControllerHandlerAdapter.handle(SimpleControllerHandlerAdapter.java:48)

at org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:923)

at org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:852)

at org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:882)

at org.springframework.web.servlet.FrameworkServlet.doPost(FrameworkServlet.java:789)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:648)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:729)


One dashboard for servers and applications across Physical-Virtual-Cloud
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y


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

Hi Daniele,

I created an account (username jeberle) on xircles.codehaus.org as stated on the GeoServer JIRA site and logged in afterwards on https://jira.codehaus.org/browse/GEOS.

I see the button “Create issue” on the top. But I cannot select GeoServer or GEOS as a project for the issue. Any hint or do I need further permissions?

Cheers,
Jonas

···

----- Am 27. Apr 2015 um 12:55 schrieb jonas eberle jonas.eberle@anonymised.com:

Hi Daniele,

thanks for your response. Unfortunately C is the case. It works fine on gray datasets. I will open an issue with a sample dataset.

Cheers,
Jonas

----- Am 27. Apr 2015 um 12:17 schrieb Daniele Romagnoli daniele.romagnoli@anonymised.com:

Dear Jonas,

I’m not sure to have fully understood your use case.

However, please note that ImageMosaic doesn’t allow to have granules with different sampleModel/colorModel within the same mosaic.

Therefore:
A) - If you are creating an ImageMosaic on a Gray dataset and then you are afterwards harvesting 1-bit paletted granules into the same mosaic, that update won’t work (by design).

B) - If you are creating an ImageMosaic on a paletted 1-bit dataset and then you are afterwards harvesting Gray Byte granules into the same mosaic, that update won’t work (by design).

C) - If you are creating an ImageMosaic on a paletted 1-bit dataset and then you are afterwards harvesting paletted 1-bit granules into the same mosaic, it should work.

D) - If you are creating an ImageMosaic on a gray dataset and then you are afterwards harvesting gray granules into the same mosaic, it should work.

If your case is one of A or B, then that it’s the expected behaviour.

If your case is one of C or D and it doesn’t work, then we should investigate on this. In that case you could open a JIRA with sample data to replicate the issue.

Please, let us know.

Hope this helps.

Cheers,

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 - 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 Sun, Apr 26, 2015 at 7:13 PM, Jonas Eberle <jonas.eberle@anonymised.com> wrote:

Dear list,

I discovered a strange behavior using the ImageMosaic Plugin. I could successfully create the imagemosaic stores using the REST interface. But when extending the store with new data using the external.imagemosaic function, some mosaic stores were not updated.

I could identify some difference in the data: If I want to use data that are converted before with the gdal_translate -co NBITS=1 command, the geoserver throws an error: WARN [gce.imagemosaic] - Failure occurred while collecting the granules. See error message below. It works fine when I do not convert the data! The imagemosaic store creation works fine for both. Just updating is not possible when data are converted before.

The relevant gdalinfo differences are listed here (first file the not converted data, second file the NBITS=1 converted data):

< Band 1 Block=17393x1 Type=Byte, ColorInterp=Gray


Band 1 Block=17393x3 Type=Byte, ColorInterp=Palette

32a34,38

Image Structure Metadata:

NBITS=1

Color Table (RGB with 2 entries)

0: 0,0,0,255

1: 255,255,255,255

Is this a known problem or can you provide any quick solution for that?

Thanks,

Jonas

26 Apr 18:15:43 WARN [gce.imagemosaic] - Failure occurred while collecting the granules

org.apache.commons.io.DirectoryWalker$CancelException: Operation Cancelled

at org.apache.commons.io.DirectoryWalker.checkIfCancelled(DirectoryWalker.java:395)

at org.apache.commons.io.DirectoryWalker.walk(DirectoryWalker.java:368)

at org.apache.commons.io.DirectoryWalker.walk(DirectoryWalker.java:335)

at org.geotools.gce.imagemosaic.ImageMosaicDirectoryWalker$MosaicDirectoryWalker.(ImageMosaicDirectoryWalker.java:114)

at org.geotools.gce.imagemosaic.ImageMosaicDirectoryWalker.run(ImageMosaicDirectoryWalker.java:196)

at org.geotools.gce.imagemosaic.ImageMosaicReader$HarvestedResource.harvestCalculation(ImageMosaicReader.java:405)

at org.geotools.gce.imagemosaic.ImageMosaicReader$HarvestedResource.access$100(ImageMosaicReader.java:187)

at org.geotools.gce.imagemosaic.ImageMosaicReader$HarvestedResource$1.harvest(ImageMosaicReader.java:202)

at org.geotools.gce.imagemosaic.ImageMosaicReader.harvest(ImageMosaicReader.java:1250)

at org.geoserver.catalog.CoverageDimensionCustomizerReader$CoverageDimensionCustomizerStructuredReader.harvest(CoverageDimensionCustomizerReader.java:128)

at org.geoserver.catalog.rest.CoverageStoreFileResource.handlePost(CoverageStoreFileResource.java:90)

at org.restlet.Finder.handle(Finder.java:296)

at org.geoserver.rest.BeanDelegatingRestlet.handle(BeanDelegatingRestlet.java:38)

at org.restlet.Filter.doHandle(Filter.java:105)

at org.restlet.Filter.handle(Filter.java:134)

at org.restlet.Router.handle(Router.java:444)

at org.geoserver.rest.RESTDispatcher$1.handle(RESTDispatcher.java:205)

at com.noelios.restlet.ext.servlet.ServletConverter.service(ServletConverter.java:129)

at org.geoserver.rest.RESTDispatcher.handleRequestInternal(RESTDispatcher.java:87)

at org.springframework.web.servlet.mvc.AbstractController.handleRequest(AbstractController.java:153)

at org.springframework.web.servlet.mvc.SimpleControllerHandlerAdapter.handle(SimpleControllerHandlerAdapter.java:48)

at org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:923)

at org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:852)

at org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:882)

at org.springframework.web.servlet.FrameworkServlet.doPost(FrameworkServlet.java:789)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:648)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:729)


One dashboard for servers and applications across Physical-Virtual-Cloud
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y


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


One dashboard for servers and applications across Physical-Virtual-Cloud
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y


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

On Mon, Apr 27, 2015 at 1:39 PM, Jonas Eberle <jonas.eberle@anonymised.com> wrote:

Hi Daniele,

I created an account (username jeberle) on xircles.codehaus.org as stated
on the GeoServer JIRA site and logged in afterwards on
https://jira.codehaus.org/browse/GEOS.

The jira server has been moved to
https://osgeo-org.atlassian.net/projects/GEOS since Codehaus is shutting
down.
Did you follow a link in the official documentation that got you to
jira.codehaus.org?

Cheers
Andrea

--

GeoServer Professional Services from the experts! Visit
http://goo.gl/NWWaa2 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 - 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.

-------------------------------------------------------

The jira server has been moved to https://osgeo-org.atlassian.net/projects/GEOS
since Codehaus is shutting down.
Did you follow a link in the official documentation that got you to
jira.codehaus.org ?

I found the link in the Readme ("Bugs" section) of the GitHub page:
https://github.com/geoserver/geoserver

Cheers,
Jonas

On Mon, Apr 27, 2015 at 2:11 PM, Jonas Eberle <jonas.eberle@anonymised.com> wrote:

I found the link in the Readme ("Bugs" section) of the GitHub page:

https://github.com/geoserver/geoserver

Ah, thanks for that, fixed it now

Cheers
Andrea

--

GeoServer Professional Services from the experts! Visit
http://goo.gl/NWWaa2 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 - 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.

-------------------------------------------------------