Chiming in and actually interrupting the thread, apologies :) What you report should not happen regardless of the reprojection.
I would need to know: - version fo geoseerver - wms resource limits configuration (especially max rendering time) - mosaic configuration ( I mean the configuration parameter for the msoaic) - structure of the underlying data Regards, Simone Giannecchini == GeoServer Professional Services from the experts! Visit http://goo.gl/NWWaa2 for more information. == Ing. Simone Giannecchini @simogeo Founder/Director GeoSolutions S.A.S. Via Poggio alle Viti 1187 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 ------------------------------------------------------- On Fri, Jun 27, 2014 at 4:29 PM, Jonathan Moules <jonathanmou...@warwickshire.gov.uk> wrote: > Hehe, have you ever tried filing a bug report with ESRI? I'll pass on that > one. ;-) > > On the whole we're happy to have GeoServer functioning with WGS:84, that's > what the KML users required. However for this particular dataset it's > causing issues. > I guess there's no way to restrict projections per layer? > > Storing the layer twice is suboptimal. It's by far our biggest layer at 30GB > of server space. > > Is this expected behaviour when warping a raster? Shouldn't it time out? I > understand WCS persevering, but not so much WMS. > > Cheers, > Jonathan > > On 27 June 2014 15:06, Ian Turton <ijtur...@gmail.com> wrote: >> >> That is clearly a *should* not a *must* (or *shall*) - so it's optional. >> File a bug report against it. >> >> Or a more practical note can you store the layer twice? >> >> Ian >> >> >> On 27 June 2014 15:00, Jonathan Moules >> <jonathanmou...@warwickshire.gov.uk> wrote: >>> >>> Hi Ian, >>> Yep, it's 6.7.3.1: >>> >>>> To maximize interoperability among servers, providers should also >>>> support geographic coordinates by geocentric coordinate systems such as >>>> “CRS:84” (see 6.7.3.2), “EPSG:4326” (see 6.7.3.3) or other ITRF-based >>>> systems. >>> >>> >>> ESRI took this to mean "we should always use this EPSG by default", hence >>> I end up with this mess. It doesn't seem to be in 1.1.0 >>> Cheers, >>> Jonathan >>> >>> >>> On 27 June 2014 13:44, Ian Turton <ijtur...@gmail.com> wrote: >>>> >>>> Are you sure about "it's in the WMS spec as mandatory" ? I'm fairly sure >>>> it isn't though I don't use 1.3 much so it may have slipped in there. >>>> >>>> Ian >>>> >>>> >>>> On 27 June 2014 13:19, Jonathan Moules >>>> <jonathanmou...@warwickshire.gov.uk> wrote: >>>>> >>>>> Hi List, >>>>> My aerial imagery is 31GB, comprising 13 optimised (tiled and >>>>> pyramided) geotiffs which make up an ImageMosaic. The imagery is in >>>>> EPSG:27700 - British National Grid. This all works fine. >>>>> >>>>> However, a certain piece of proprietary GIS software (namely ESRI) is >>>>> incapable of automatically using the native projection and instead >>>>> requests >>>>> the layer in EPSG:4326 whenever it's added. >>>>> >>>>> The request is: >>>>> >>>>> >>>>> http://example.com/gs/ows?SERVICE=WMS&VERSION=1.3.0&REQUEST=GetMap&CRS=CRS:84&BBOX=-1.9868610903408341,51.938491047471814,-1.1430930819885086,52.705668101075581&WIDTH=919&HEIGHT=836&LAYERS=Aerial_Photography%3aAerial_Photography_2013&STYLES=&EXCEPTIONS=XML&FORMAT=image/png&BGCOLOR=0xFEFFFF&TRANSPARENT=TRUE >>>>> >>>>> This then proceeds to hammer GeoServer which maxes out its allocated >>>>> RAM, uses 100% of one core of the CPU it's on, and becomes generally much >>>>> less responsive. The request never seems to time out, it just keeps >>>>> processing indefinitely. >>>>> >>>>> I appreciate that warping is a computationally hard problem, but >>>>> shouldn't there be some sort of built in clean up to stop this? >>>>> My WMS "resource consumption limits" are all at the defaults. >>>>> The tomcat localhost_access.log doesn't even show the request, even 11 >>>>> mins later - I have to use Fiddler. >>>>> >>>>> Any suggestions for how to handle this situation? It's impossible to >>>>> remove EPSG:4326 from the CRS list (it's in the WMS spec as mandatory), >>>>> and >>>>> it's impossible to get ArcGIS to behave properly, so is there another >>>>> solution that entails getting GeoServer to work smarter? >>>>> >>>>> Cheers, >>>>> Jonathan >>>>> >>>>> This transmission is intended for the named addressee(s) only and may >>>>> contain confidential, sensitive or personal information and should be >>>>> handled accordingly. Unless you are the named addressee (or authorised to >>>>> receive it for the addressee) you may not copy or use it, or disclose it >>>>> to >>>>> anyone else. If you have received this transmission in error please notify >>>>> the sender immediately. All email traffic sent to or from us, including >>>>> without limitation all GCSX traffic, may be subject to recording and/or >>>>> monitoring in accordance with relevant legislation. >>>>> >>>>> ------------------------------------------------------------------------------ >>>>> Open source business process management suite built on Java and Eclipse >>>>> Turn processes into business applications with Bonita BPM Community >>>>> Edition >>>>> Quickly connect people, data, and systems into organized workflows >>>>> Winner of BOSSIE, CODIE, OW2 and Gartner awards >>>>> http://p.sf.net/sfu/Bonitasoft >>>>> _______________________________________________ >>>>> Geoserver-users mailing list >>>>> Geoserver-users@lists.sourceforge.net >>>>> https://lists.sourceforge.net/lists/listinfo/geoserver-users >>>>> >>>> >>>> >>>> >>>> -- >>>> Ian Turton >>> >>> >>> >>> This transmission is intended for the named addressee(s) only and may >>> contain confidential, sensitive or personal information and should be >>> handled accordingly. Unless you are the named addressee (or authorised to >>> receive it for the addressee) you may not copy or use it, or disclose it to >>> anyone else. If you have received this transmission in error please notify >>> the sender immediately. All email traffic sent to or from us, including >>> without limitation all GCSX traffic, may be subject to recording and/or >>> monitoring in accordance with relevant legislation. >> >> >> >> >> -- >> Ian Turton > > > > This transmission is intended for the named addressee(s) only and may > contain confidential, sensitive or personal information and should be > handled accordingly. Unless you are the named addressee (or authorised to > receive it for the addressee) you may not copy or use it, or disclose it to > anyone else. If you have received this transmission in error please notify > the sender immediately. All email traffic sent to or from us, including > without limitation all GCSX traffic, may be subject to recording and/or > monitoring in accordance with relevant legislation. > > ------------------------------------------------------------------------------ > Open source business process management suite built on Java and Eclipse > Turn processes into business applications with Bonita BPM Community Edition > Quickly connect people, data, and systems into organized workflows > Winner of BOSSIE, CODIE, OW2 and Gartner awards > http://p.sf.net/sfu/Bonitasoft > _______________________________________________ > Geoserver-users mailing list > Geoserver-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/geoserver-users > ------------------------------------------------------------------------------ Open source business process management suite built on Java and Eclipse Turn processes into business applications with Bonita BPM Community Edition Quickly connect people, data, and systems into organized workflows Winner of BOSSIE, CODIE, OW2 and Gartner awards http://p.sf.net/sfu/Bonitasoft _______________________________________________ Geoserver-users mailing list Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users
