Tag Info

Hot answers tagged

6

You need to specify a min/max scale denominator in your SLD files. Use the same figure in each style, that is the max in one is the min in the other, so that only one layer is drawn at any scale. Then combine the layers in a layer group and away you go. See http://docs.geoserver.org/latest/en/user/styling/sld-reference/rules.html for more details on the ...


5

You didn't include properties in the right place. Then again, you also didn't include working code, so perhaps this isn't your actual code, but the four args to WMS are: name URL Properties (sent to server) Options (used on the client) So your code should look something like this: var demolayer = new OpenLayers.Layer.WMS( "Eg", ...


5

Below is an example of an SLD rule that places a label at the center of a feature's geometry. This uses the ogc:Function called "centroid" to place the label. You can read more about SLD functions in the GeoServer docs, and some examples are given here. <sld:Rule> <MaxScaleDenominator>5000</MaxScaleDenominator> ...


5

What you have found is something in the OpenLayers sand box, which is an environment where OpenLayers contributors can add their own custom layers, controls, etc. Sometimes things created in the sand box work their way through to the core distribution. However, it is simple to take what has been created and add it to your OpenLayers build. First, you need ...


5

The table gt_pk_metadata is an optional table that GeoTools (and GeoServer) use to work out what the primary key columns in a view are. It is needed to generate consistent feature IDs (FIDS) otherwise GeoTools will use the feature's java ID which will change from run to run. It is explained in this document. So you can ignore this error if you don't care ...


4

Not me but Adrian Walker has 'Using Ordnance Survey OpenData Street View Rasters With GeoServer' http://www.adrianwalker.org/2010/08/using-ordnance-survey-open-data-street.html Some good tips there (especially if on linux platform) Some python code is available at the bottom. Or are you looking for Vector examples? ...


4

Update See responses to Radek's post in the GWC forum for actual cause and solution. I now understand why TileCache opted for displaying errors such as "Current x value -1311047.936977 is too far from tile corner x -1493907.560000" rather than passing back the "closest" tiles within an arbitary error range. Is your original data in EPSG 3857? If not ...


4

Support for translucency in PNG8 has been added in 2.2.x: http://geo-solutions.blogspot.it/2012/05/developers-corner-geoserver-stunning.html


4

The idea behind GeoWebCache is that if a tile is available in the cache it will grab it and send it back to the client, it won't even bother making the round trip to your database. So it won't make a call to the SQL Server database unless the tile is not there. The trip to the SQL database is exactly what you are trying to cut out by using GeoWebCache, if it ...


3

The GWC integrated with GeoServer automatically drops the tiles involved when doing a WFS-T transaction in GeoServer. If you are changing data directly in PostGIS you can look at publishing data change events using a GeoRSS feed: http://geowebcache.org/docs/current/configuration/layers/georss.html


3

There was a mention of a TileCache patch for this on the OSGeo mailing lists: http://www.osgeo.org/pipermail//tilecache/2009-June/001863.html Unfortunately the links to the patches no longer work. Apparently the patch involved a few changes to the code base, and would allow different caches to be used based on any URL argument. I have an old script (in ...


3

The correct url for the legend graphic for each layer and style is embedded in the GetCapabilities response as the LegendURL element. To get it: fetch the capabilities xml document parse it (OpenLayers has a parser class) retrieve the LegendURL for each layer you're interested in Alternatively you can build a GetLegendGraphic request by following the ...


3

Do you have the correct tile-origin set for your OpenLayers.Map as in GeoWebCache. Check how the TileOrigin is set in the GeoWebCache-demo of the layer and make sure you have the same TileOrigin on your OpenLayers.Map Constructor.


3

Misalignment such as this is almost always a projection issue. Is the data stored in EPSG:3857? Check that the GeoWebCache layer is configured to output in EPSG:3857.


3

A partial answer here. Have you seen the following resources? http://geowebcache.org/docs/current/introduction/whichgwc.html If you have one geoserver then use the integrated geowebcache otherwise use the standalone GWC to connect to multiple geoservers. http://opengeo.org/publications/geoserver-production/ OpenGeo certainly recommend using the latest ...


3

Tomcat and Geoserver need write permissions. You need to give tomcat7 ownership of /opt/gwc


2

http://docs.geoserver.org/stable/en/user/geowebcache/setup.html GeoWebCache does not work when multiple GeoServer instances are configured to use the same data directory. The H2 database crashes during initialization when the second instance is started. Two possible workarounds: Delete gwc*.jar in WEB-INF/lib and restart GeoServer. This disables ...


2

Have you tried clearing the cache?


2

Make sure you name the layer in geowebcache.xml with a different name to the one in GeoServer. Hand edit the file /workspaces////layer.xml and set the following metadata property: EPSG:4326,EPSG:900913,EPSG:27700


2

GWC doesn't do reprojection, so you need to download GeoServer 2.1 and set up your remote WMS as a cascading WMS, GeoServer will then reproject your remote WMS from 4326 to what ever projection you need. Then use the built in GWC to serve out tiles from the cascaded layer. This blog post ...


2

There is no easy configuration option to do so but I believe the "backend storage" in geowebcache is pluggable... so it might be possible to write a custom storage backend that uses the same format as slippy map. I would post to the geowebcache-devel list and ask there.


2

No matter which way you slice it, you'll need a load of disk space to store those images. I wouldn't recommend using an index colour format because it'll look pretty darn awful. The resolution is really dependent on what your clients will be doing with the imagery, and whether they'll be happy losing features smaller than 25m. A way to reduce the size of ...


2

As per the documentation, switching from WMS to GeoWebCache only requires a URL change from: /geoserver/wms <- direct WMS /geoserver/gwc/service/wms <- geocached wms and you're good to go, no need to switch WMTS. BTW, GeoWebCache requires all tiles be 256x256. You can also seed the cache from the GeoCache home that can be reached from the ...


2

I'm afraid it's not possible. In the most recent version GWC (starting from 1.3 RC1) will simply throw an error while before it used to rely the request to the upstream WMS (without caching the response). The reason is that GWC align tiles to Google Maps as stated in this email: ...


2

i want to say some solutions come to my mind. 1.check out GeoWebCache endpoint URL as http://example.com/geoserver/gwc/service/wms for GeoWebCache WMS instead. 2.check out your geowebcache.xml and openlayers whether same projection or not. 3.check out GeoWebCache demo page from http://localhost:8080/geoserver/gwc/demo. 4.check out your GeoWebCache ...


2

If you want to cache tiles in projections other than the two defaults (4326, 900913) then you need to define a custom gridset with the new projection so that tiles in that projection are created. The process is a little bit involved but is explained at http://geowebcache.org/docs/current/configuration/layers/projections.html


2

One option is create trigger into postgis table which uses "NOTIFY channel_name message" when something happens. Then create softaware which conencts to postgresql and executes "LISTEN channel_name" and when something happens on channel it executes command which re-creates tiles. You can forward needed coordinates with in message


2

GWC and raster2pgsql do quite different things. They both use image tiles, but use them to do very different things. raster2pgsql is a way to store a large raster data sets inside Postgres. The tiles are an implementation detail used to allow for faster lookup of subsets of the raster and have no impact on what's served up by GeoServer in a WMS or WCS. ...


2

Known issue, Windows specific, has been fixed in the 2.3.x series: http://jira.codehaus.org/browse/GEOS-5536


2

You should be able to do this easily through the web interface (ie http://yourserver:8080/geoserver/web). First log in, go to Tile Layers under the Tile Caching heading (left side). One there, click on 'Seed / Truncate' next to the layer you are concerned with. You can set the parameters of the seed/truncate towards the bottom on that window. Most ...



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