- WMSGetFeatureInfo with Geoserver HTTP Auth
I’m using Geoserver and OpenLayers to call Geowebcache with WMS layers. My application and Geoserver are on different servers so I’m using OpenLayer.ProxyHost and a URL rewrite on the map server. We just added access rules to the layers with data security in Geoserver. I was able to get the layers to show up on the map by using this answer:
I can’t get the wmsgetfeatureinfo to work, though. Even after I ‘login’ to geoserver and that cookie gets set, it still won’t let me click. I think it might have something to do with the proxies and the authentication not getting passed all the way through. How do I fix this so I can click on the points again? Even if it’s not with wmsgetfeatureinfo?
- GeoServer Raster Data Sources: satellite data’s contrast issue
I am trying to use my own satellite image as the basemap for a webapp, instead of OSM, Google etc imageries. In order to do that, I made a
Raster Data Sourcesstore inside my GeoServer, which is pointing towards a .tif file (having .prj and .tfw files along-with). I am on Ubuntu 14.04. Everything is working fine except the following issue.
As can be seen in the attached images, visualization of satellite image in QGIS is giving a good contrast and brightness. But importing the very same image inside GeoServer is producing low contrast/bright image, plus seams, which can be seen at the bottom section. Although I am using
Tiling:Tiledin the GeoServer, it shouldn’t create seams. Zoomin and out are also changing the contrast and brightness of the GeoServer image.
Kindly explain the reason and remedy of this unexpected effect.
Digest powered by RSS Digest