Tag Info

Hot answers tagged

4

So the environment variable you're setting is a "User Variable". It applies only to the user you're editing it as. You need to edit the environment for at least the user that your geoserver is running as. See http://technet.microsoft.com/en-au/library/cc772047.aspx for how to set an environment variable using GPOs. Probably the easiest way is to just make ...


3

If you add LEGEND_OPTIONS parameter to your request and the value forceLabels:on then you can force GeoServer to draw the text for a single rule. Here is an example of a request: ...


2

1. Connect to Catalog cat = Catalog("http://localhost:8080/geoserver/rest","admin", "geoserver") 2. Get some layers and styles lyrs = [list of layers] stls = [list of styles] 3. Create the group layer lg = cat.create_layergroup(groupname) 4. Add the layers and styles to the group layer lg.layers = lyrs lg.styles = stls 5. Save the group ...


2

Besides the view, the only other possibility that comes to mind is to teach GeoServer to recognize these fields by improving its code. You can ask on the geotools-devel/geoserver-devel mailing list for directions, if you plan to do it yourself, or check the commercial support links at geotools.org and geoserver.org


2

You need to initialize your map object. See the source code here for an example: http://leafletjs.com/examples/quick-start-example.html Add something like this to harris.js before you call map.on. var map = L.map('map').setView([51.505, -0.09], 13); What's happening is map.on is undefined. Map itself is not defined in JavaScript, but by default DOM ...


2

Brad answer is spot on. However, there has been a desire to also allow admins to setup dynamic bounding boxes on selected layers, it just needs someone to implement it / sponsor it.


1

If you edit your code this way, it works (note the ADDED line) var Markerlayer = L.geoJson(null, { pointToLayer: function(feature, latlng) { marker = L.marker(latlng, {}); marker.options['title'] = feature.properties['uname']; // ADDED return marker; }, onEachFeature: function(feature, ...


1

Ok, problem solved. Like I said early, the problem was in the resolutions, or better, in the zoom. If you use a max resolution or an array of resolutions(along with restricted extent), OpenLayers will ask to the server for the first set of tiles, which is not what I wanted. To fix the problem, you must tell the server that you want to start from the set of ...


1

The documentation for params is correct when it says: "At least a LAYERS param is required. STYLES is '' by default. VERSION is 1.3.0 by default. WIDTH, HEIGHT, BBOX and CRS (SRS for WMS version < 1.3.0) will be set dynamically.". So when you want to set SLD_BODY, you also have to unset STYLES: source.updateParams({STYLES: undefined, SLD_BODY: ...


1

Basic rule for OpenLayers and WFS is that do not test with OpenLayers. With a browser you can control what happens. Some first steps to take: How many features there are in the service? http://demo.opengeo.org/geoserver/wfs?service=wfs&version=1.1.0&request=getfeature&typename=topp:states&resulttype=hits Can you get all data out in default ...


1

You can go to geoserver administration page, go to Style memu and then edit that sld style. There should be tags like <name> and you can change it.


1

If you do not have to support very old browsers, the easiest way to achieve this is to make the servlet container that your GeoServer runs in (e.g. Tomcat) send CORS headers. A good web site that explains how to set these for all different kinds of servers is http://enable-cors.org. You may not want to allow cross-domain requests from all hosts, so you ...


1

Googling, I've found an answer that can help you to set CORS if serving with Tomcat. CORS help you change Ajax "same origin policy" between domains. Another alternative can be to use ARR (Application Request Routing) to use IIS as a proxy so everything seems to be coming from the same IP and you avoid same origin policy error you have at the moment; See ...


1

Your problem seems to be investigated on the GeoServer developer mailing list in this thread Summary Cascading WMS from the Polish geoportal is failing because the server does not accept Java as a User-Agent in the http headers. I recommend to contact the administrators of the geoportal because this behavior it preventing the use of the WMS service with ...


1

I can see that this question is similar to How to Start Web Mapping?, but it is slightly different since the OP has zeroed in on a Stack; Hence I think it merits an proper answer. All of the softwares that you mentioned, work with each other, and truly understand them, you should learn them simultaneously. I'll recommend that you start with this Penn ...


1

if you are using geoserver built in geowebcache, this issue cen be occured. I recommand you that install a standalone geowebcacbe. Standalone installation is working fine.


1

Instead of using vectors to represent this (as you are aggregating to a grid), why not use a raster? You could generate rasters at different resolutions reflecting your grid size. You can do this in PostGIS. I would do it using the following approach: create a grid of polygons at each of your zoom scales aggregate the points per grid using the criteria ...


1

This issue has been discussed on the GeoServer mailing list here: http://comments.gmane.org/gmane.comp.gis.geoserver.user/44081 Basically this comes from a (faulty) security update from Microsoft that has been updated, see this link from MS: https://support2.microsoft.com/kb/2992611


1

Found what was the problem. Following that example, I thought that that syntax was referring to properties inside OpenLayers. Instead it wasn't. Where you have to indicate the style, you have to put the name of the namedLayer of your sld, like so: var format = new OpenLayers.Format.SLD(); OpenLayers.Request.GET({ url: 'style/roadsStyle.xml', ...


1

Using the WMSGetFeatureInfo method, the way to pass along viewparams is by using vendorparams and and assigning the viewparams in the eventlistener before the callback function retrieving the "click result" from the WMS layer click_info = new OpenLayers.Control.WMSGetFeatureInfo({ title: 'Identify features by clicking', layers: ...



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