Hot answers tagged wms
According to a recent comparison of different mapping engines in performing tile seeding (see Section 4.3), MapServer should be much faster than GeoServer. Is there any re-projection of geometries in your rendering stack? An old version of MapServer might have the same issue with proj4 lib as Mapnik had.
It's been added since 2.7.1. See release note here. Here the JIRA report. Simone.
This is being worked on at the Time Manager plugin right now https://github.com/anitagraser/TimeManager/pull/134 And here is a small animation: http://postimg.org/image/nvoqb9uc5/
There currently is an awkward level of WMS-T support in QGIS--you put the TIME parameter in the WMS URL and tell it to use your given URL that instead of the URLs in the GetCapabilities document. You can get a specific time from the NEXRAD WMS-T server into QGIS by using a URL string like the below in Layer/Add WMS/WMTS layer/New/URL : ...
I've created a feature request for this functionality https://hub.qgis.org/issues/13085
To start with read the WMS Spec so that you have an understanding of how they work. If you look in the GetCapabilities file you will see the layer with the title "GDPS.ETA - Air temperature" has the following definition: <Layer queryable="1" opaque="0"> <Name>GDPS.ETA_TT</Name> ...
Anti-meridian behavior is undefined in MapProxy right now (1.8). For most users it's is not an issue and so no one invested time or money to work on this. I know that this is not great for people from "the edge of the world" and I hope that this will change in the future.
This is just a guess, but I assume, its about the distortion inherent to your Projection EPSG:3574 which is extremal because displaying the pole(s). I guess there's only data in your raster layer until around 85°N or something, and you are trying to display data further north. You could try a projection that is "closer" to EPSG:4326 and then also first ...
You are not telling us how you get the WMS in Leaflet: are you using the default object or a plugin? I have experiences the "cut" issues with labels too. I suspect that the problem might come from the fact that Leaflet WMS object is a extension of the Tile object and somehow in the request processing somehting ges wrong. The geometric object to which the ...
I will try to be as clear as possible, but I am not sure I understood everything that your are asking. You might want to edit your post with additional information or a concrete example and the version of Geoserver you are using. Problem 1: you have duplicate labels due to the tiling of your WMS request by OL -> solution: in Open Layer, request a single ...
You have probably hit a side effect of heavy work what was done with GeoServer GetFeatureInfo to return info from what is exactly rendered on the map. With the style used in your map there is nothing rendered between the markers. You can have a try by adding a buffer vender parameter into your GetFeatureInfo request. The default value is 3, try to add ...
Only top voted, non community-wiki answers of a minimum length are eligible