Tag Info

Hot answers tagged

4

You can only use a x,y (i,j) coordinate search for GetFeatureInfo requests http://docs.geoserver.org/stable/en/user/services/wms/reference.html#getfeatureinfo However, you may test for interactions with polygons (and many other geometries) using a Web Feature Service (WFS) request. E.g. ...


2

The best reference for this is this page on the OSM Wiki. It has Pseudo code as well as code in various languages for converting from the XYZ tilenames, to the bounding box. The Pseudocode for this is as follows n = 2 ^ zoom lon_deg = xtile / n * 360.0 - 180.0 lat_rad = arctan(sinh(π * (1 - 2 * ytile / n))) lat_deg = lat_rad * 180.0 / π Note that this ...


2

It is up to the WMS server admin which formats the server is configured to support for GetFeatureInfo. Check from the GetCapabilities of the WMS server the list of supported INFO_FORMATs. Geoservers by default support geojson and GML info formats and those include also geometries with GetFeatureInfo results. You can try with the following links: ...


1

You seem to be right and server wants BBOX coordinates in lon-lat order even it claims that it is a WMS 1.3.0 server. This brings the whole world from east to west ...


1

Sure, it takes time to process all those vertices and render them down to the raster. And if you have enough vertices, they probably don't add any information to the picture at all. Like, if you have a river with 1000 vertices and map it into a 1000x1000 image, you might get one vertex per pixel, but probably you'll end up with lots of pixels with more than ...


1

The proper way to set the maximum level of a WMS layer is the use of rules in the style associated with the layer. If you are afraid that users can zoom out of 1:1000 with other style, you can define only one style associated with the layer.



Only top voted, non community-wiki answers of a minimum length are eligible