Hi, Unfortunately you have obviously wasted a lot of time by searching a problem from a totally wrong direction. If you want to change GetMap request from WMS 1.3.0 into WMS 1.1.0 you must study the differences between the standard versions and then
1) change version=1.3.0 ->1.1.0 2) change CRS= -> SRS= 3) check what projection you have and if it is some with official latitude-longitude or northing-easting axis order flip the bbox Try this http://data.fao.org/maps/wms?styles=geonetwork_sea_7379_style&LAYERS=GEONETWORK%3Asea_7379&FORMAT=image%2Fpng&TRANSPARENT=TRUE&VERSION=1.1.1&LANGUAGE=eng&EXCEPTIONS=INIMAGE&SERVICE=WMS&REQUEST=GetMap&SRS=EPSG%3A4326&BBOX=30.758972167957,5.519599914545,36.658630371082,8.25519561767&WIDTH=537&HEIGHT=249 -Jukka Rahkonen- -----Alkuperäinen viesti----- Lähettäjä: benve [mailto:[email protected]] Lähetetty: 28. marraskuuta 2017 11:54 Vastaanottaja: [email protected] Aihe: Re: [Geoserver-users] Redirecting from external server to web application passing through a Geoserver --> Version problem? Dear Jukka, I also could not find this layer by simply stating the end point as Capabilities URL, although I had 1000 potential layers that could be published if I do so. In order to publish this exact layer in Geoserver through the WMS cascading I needed to specify the style "geonetwork_sea_7379_style" and the layer name "GEONETWORK:sea_7379" after the end point. Please use this link to make it happen: http://data.fao.org/maps/wms?styles=geonetwork_sea_7379_style&LAYERS=GEONETWORK:sea_7379&version=1.3.0 Only in this way, Geoserver proposed me to publish this layer. If you want to experience the problem of data not being shown on map, you can simply do it in Chrome: Use the endpoint of FAO, change the VERSION from 1.3.0 to 1.1.0. With such a bbox you'll see data becoming invisible with version 1.1.0. http://data.fao.org/maps/wms?styles=geonetwork_sea_7379_style&LAYERS=GEONETWORK%3Asea_7379&FORMAT=image%2Fpng&TRANSPARENT=TRUE&VERSION=1.3.0&LANGUAGE=eng&EXCEPTIONS=INIMAGE&SERVICE=WMS&REQUEST=GetMap&CRS=EPSG%3A4326&BBOX=5.519599914545,30.758972167957,8.25519561767,36.658630371082&WIDTH=537&HEIGHT=249 You can also use the first link to connect through ArcGis. You'll see the data is properly visualized and that the WMS request is automatically set to 1.3.0. The fact that the layer was not visible through GetCapabilities from FAO if the style of the layer was not specified, and the fact that I have this problem in visualizing data from FAO with a 1.1.0 WMS request, suggested me that the problem could be related to the fact that important information on the way the layer is rendered are contained in the style of the layer, which I believe could not be properly read if the WMS request is not performed with the 1.3.0 version. When I redirect the data through the Geoserver that I use at work data becomes invisible with high zoom as it does if I stream data from FAO with a 1.1.0 WMS version. However, it doesn't matter whether I state version 1.1.0 or 1.3.0 in Geoserver. The problem is constant. This is why I thought that Geoserver was reading the data from the FAO endpoint through a 1.1.0 version and that therefore the specification of a more recent version of WMS request from the Geoserver to the environment where I finally visualize the data could not change the way the data were rendered. Finally, keep in mind that I'm working on a web application where I can visualize spatial data that can be streamed through WMS requests only through https connections. FAO doesn't offer a https connection, thus I redirect the FAO data through the Geoserver that I employ where I work (which offers https connections). This is something I do with many other data and I've never had such problems. This is the only case where I don't manage to properly visualize the data in the web application. If you have any idea on how I could force Geoserver to read the data properly please let me know. Thanks, Antonio -- Sent from: http://osgeo-org.1560.x6.nabble.com/GeoServer-User-f3786390.html ------------------------------------------------------------------------------ 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 Please make sure you read the following two resources before posting to this list: - Earning your support instead of buying it, but Ian Turton: http://www.ianturton.com/talks/foss4g.html#/ - The GeoServer user list posting guidelines: http://geoserver.org/comm/userlist-guidelines.html [email protected] 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 Please make sure you read the following two resources before posting to this list: - Earning your support instead of buying it, but Ian Turton: http://www.ianturton.com/talks/foss4g.html#/ - The GeoServer user list posting guidelines: http://geoserver.org/comm/userlist-guidelines.html [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-users
