For your information, I have created an issue related to &version=1.3.0 ImageMosaic layers problem. See, http://jira.codehaus.org/browse/GEOS-6651
Ville Karppinen ________________________________________ From: Jody Garnett [[email protected]] Sent: Friday, September 05, 2014 21:40 To: Ville Karppinen Cc: [email protected] Subject: Re: [Geoserver-users] Gs 2.5.2 exception: crs must be the same for all objects I see you are working with raster layers, I had assumed based on your description you had set up a table with miss matched geometries (sometimes people do!) Can you report your issue to the issue tracker? It is very close to the 2.6.0 release and they may not be time to address it in time :( Jody Garnett On Fri, Sep 5, 2014 at 3:42 AM, Ville Karppinen <[email protected]<mailto:[email protected]>> wrote: It seems that there is some bug related to this issue in GeoServer 2.5.2 and it is also in the 2.5-SNAPSHOT (build date = 03-Sep-2014 15:29). The problem seems to be more general than I mentioned before (not limited to elevations) and seems to be related to imagemosaicking plugin when using &version=1.3.0. It seems that geoserver does not work properly when version 1.3.0 is used for ImageMosaic layers. This can easily be reproduced with the GeoServer 2.5.2 release version and by previewing ImageMosaic layer nurc:mosaic which is given as one of the default layers. When version number in URL is changed to 1.3.0 image is not shown. For example: when using OpenLayers preview: http://localhost:8080/geoserver/nurc/wms?service=WMS&version=1.3.0&request=GetMap&layers=nurc:mosaic&styles=&bbox=6.346,36.492,20.83,46.591&width=512&height=356&srs=EPSG:4326&format=application/openlayers which seems to use following URL for an image: http://localhost:8080/geoserver/nurc/wms?LAYERS=nurc%3Amosaic&STYLES=&FORMAT=image%2Fjpeg&SERVICE=WMS&VERSION=1.1.1&REQUEST=GetMap&SRS=urn%3Ax-ogc%3Adef%3Acrs%3AEPSG%3A4326&BBOX=-0.896,31.47059375,28.072,51.61240625&WIDTH=512&HEIGHT=356 which does not work because of the &SRS value, works if using &SRS=EPSG%3A4326 Also, image is not given properly if version 1.3.0 is used instead of 1.1.1: http://localhost:8080/geoserver/nurc/wms?LAYERS=nurc%3Amosaic&STYLES=&FORMAT=image%2Fjpeg&SERVICE=WMS&VERSION=1.3.0&REQUEST=GetMap&SRS=EPSG%3A4326&BBOX=-0.896,31.47059375,28.072,51.61240625&WIDTH=512&HEIGHT=356 ImageMosaic layer seems to work fine when using &version=1.1.1 or even with 1.3 work but 1.3 is not proper version number according to standard. Also, it seems that 1.3.0 problem is limited only to ImageMosaic layers. Best regards, Ville Karppinen [email protected]<mailto:[email protected]> +358407509542<tel:%2B358407509542> On 09/03/2014 02:05 PM, Ville Karppinen wrote: Hi, I updated GeoServer from 2.5 version to 2.5.2. After this update, geoserver started to give exception for layers that have multiple elevations and use different bounding boxes for different elevations when using service=WMS&version=1.3.0. The exception is: "Error rendering coverage on the fast path org.opengis.geometry.MismatchedReferenceSystemException: The coordinate reference system must be the same for all objects. The coordinate reference system must be the same for all objects." I tried to google some tips for this but did not find any. I would like to know if there is any way, for example, to configure geoserver to allow different bboxes for different elevations in a single layer? Best regards, ------------------------------------------------------------------------------ Slashdot TV. Video for Nerds. Stuff that matters. http://tv.slashdot.org/ _______________________________________________ Geoserver-users mailing list [email protected]<mailto:[email protected]> https://lists.sourceforge.net/lists/listinfo/geoserver-users ------------------------------------------------------------------------------ Slashdot TV. Video for Nerds. Stuff that matters. http://tv.slashdot.org/ _______________________________________________ Geoserver-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-users
