Thanks Arne.

Ok, then, perhaps there is a way to disable the automatic geowebcache
configuration generation in the GeoServer implementation?

>From the GeoServer docs:
http://geoserver.org/display/GEOSDOC/5.+GWC+-+GeoWebCache

*"The integrated version of GeoWebCache automatically configures every layer
with the two most common projections:*

   - *EPSG:4326 (standard Latitude/Longitude)*
   - *EPSG:900913 (Spherical Mercator, the projection used in Google Maps)"*

Thanks!

Roger

On Mon, Dec 13, 2010 at 2:08 PM, Arne Kepp <[email protected]> wrote:

> I wouldn't say "by design", but pretty much only grid sets and image
> formats are merged.
>
> This goes back to version 0.7-something and is fine for quick
> experimentation, but I recommend that people define the entire configuration
> in a static geowebcache.xml document for production.
>
> -Arne
>
>
>
> On 12/13/10 1:18 PM, Roger Bedell wrote:
>
>> Good afternoon Arne,
>>
>> About a year ago, to eliminate the problem of white lines around the
>> metatiles in GWC when using WMS Bilinear or "Bibubic" (someone needs to fix
>> that spelling eh?) interpolation you gave me this advice, which works
>> admirably:
>>
>> >>"In the latest GWC a "gutter" function was introduced, a buffer around
>> each image that gets sliced away. That would probably fix this, as long as
>> you don't have labels that get cut off."<<
>>
>> However, I really want to be able to modify existing layers in my
>> Geowebcache.xml, rather than having to create new names for the ones in
>> geowebcache.xml. Unfortunately, the merging of attributes specified in
>> geowebcache.xml with the ones automatically generated doesn't seem to work.
>> In particular, the "gutter" setting doesn't merge.
>>
>> To reproduce: Using the standard "latest nightly" WAR from last night, and
>> the standard data, I've done the following. Please give it a try, it will
>> only take a couple minutes, perhaps you will see the problem right away.
>>
>> 1) Set up a clean Geoserver using the standard data. (I'm using Tomcat,
>> but it shouldn't matter)
>> 2) Add the geowebcache.xml below to the <tomcat_dir>/temp/geowebcache
>> (note, the default geowebcache location doesn't seem to be in the data
>> directory anymore...)
>> 3) Start Geoserver and set the WMS default interpolation to Bilinear or
>> "Bibubic".
>> 4) Go to the GWC automatically generated demos. Click on the PNG 4326
>> examples for both the nurc:mosaic and the nurc:mosaic_1 layers.
>>
>> nurc:mosaic will have the ugly white lines, and nurc:mosaic_1 will be
>> perfect.
>>
>> My question is whether the "gutter" setting in the Geowebcache.xml should
>> override the automatically generated one for nurc:mosaic? One would think
>> so, but perhaps this is by design?
>>
>> Best regards,
>> Roger Bedell
>> Coordinate Solutions Inc.
>>
>> The test geowebcache.xml file:
>>
>> <gwcConfiguration xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
>>                  xsi:noNamespaceSchemaLocation="
>> http://geowebcache.org/schema/1.2.2/geowebcache.xsd";
>>                  xmlns="http://geowebcache.org/schema/1.2.2";>
>> <version>1.2.2</version>
>> <backendTimeout>120</backendTimeout>
>> <cacheBypassAllowed>true</cacheBypassAllowed>
>> <layers>
>>
>> <!-- GWC definition for the standard nurc:mosaic, just for PNG and just
>> for 4326 -->
>> <wmsLayer>
>> <name>nurc:mosaic</name>
>> <mimeFormats>
>> <string>image/png</string>
>> </mimeFormats>
>> <grids>
>> <entry>
>> <srs>
>> <number>4326</number>
>> </srs>
>> <grid>
>> <srs>
>> <number>4326</number>
>> </srs>
>> <dataBounds>
>> <coords>
>> <double>6.346</double>
>> <double>36.492</double>
>> <double>20.83</double>
>> <double>46.591</double>
>> </coords>
>> </dataBounds>
>> <gridBounds>
>> <coords>
>> <double>-103.87</double>
>> <double>44.37</double>
>> <double>-103.62</double>
>> <double>44.50</double>
>> </coords>
>> </gridBounds>
>> <zoomStart>0</zoomStart>
>> <zoomStop>20</zoomStop>
>> </grid>
>> </entry>
>> </grids>
>> <wmsUrl>
>> <string>http://localhost:8080/geoserver/wms</string>
>> </wmsUrl>
>> <wmsLayers>nurc:mosaic</wmsLayers>
>> <!--This doesn't seem to merge with the automatically generated
>> nurc:mosaic value!-->
>> <gutter>20</gutter>
>> </wmsLayer>
>>
>> <!-- This layer is identical to the nurc:mosaic, but just with a different
>> GWC name. -->
>> <wmsLayer>
>> <name>nurc:mosaic_1</name>
>> <mimeFormats>
>> <string>image/png</string>
>> </mimeFormats>
>> <grids>
>> <entry>
>> <srs>
>> <number>4326</number>
>> </srs>
>> <grid>
>> <srs>
>> <number>4326</number>
>> </srs>
>> <dataBounds>
>> <coords>
>> <double>6.346</double>
>> <double>36.492</double>
>> <double>20.83</double>
>> <double>46.591</double>
>> </coords>
>> </dataBounds>
>> <gridBounds>
>> <coords>
>> <double>-103.87</double>
>> <double>44.37</double>
>> <double>-103.62</double>
>> <double>44.50</double>
>> </coords>
>> </gridBounds>
>> <zoomStart>0</zoomStart>
>> <zoomStop>20</zoomStop>
>> </grid>
>> </entry>
>> </grids>
>> <wmsUrl>
>> <string>http://localhost:8080/geoserver/wms</string>
>> </wmsUrl>
>> <wmsLayers>nurc:mosaic</wmsLayers>
>> <!--This works here...-->
>> <gutter>20</gutter>
>> </wmsLayer>
>> </layers>
>> </gwcConfiguration>
>>
>>
>
------------------------------------------------------------------------------
Lotusphere 2011
Register now for Lotusphere 2011 and learn how
to connect the dots, take your collaborative environment
to the next level, and enter the era of Social Business.
http://p.sf.net/sfu/lotusphere-d2d
_______________________________________________
Geoserver-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Reply via email to