Jody,
Is it possible to get the patch (Arne ?), or am I better off trying to use
geowebcache as a separate WAR ?
Sorry, the odd behaviour is that
1) Geoserver is creating Directories in the disk cache called
EPSG_4283_topp_100ktopo_01, 02 etc despite a custom Grid being defined
“GDA94”
2) Requests that used to work fine are now not working and return
errors on the tilesize
3) The GDA94 cache is used when I zoom down a few levels, and then
suddenly geoserver creates directories called EPSG_4283_topp_100ktopo_04 and
generates tiles in those. What the ???
I’d like to have a working disk cache again, but more importantly I’d like
to be able to understand how the heck it is meant to be setup, because
fairly obviously I am missing something with the custom grid. I’d like to
remove the default 4326 and 900913 as we never use them.
I’ve been looking for a well explained working example as the docs really
don’t cut it for me.
Regards,
Shaun
________________________________
From: Jody Garnett [mailto:jody.garnett@anonymised.com]
Sent: Sunday, 22 August 2010 8:55 PM
To: Kolomeitz Shaun
Cc: geoserver-users@lists.sourceforge.net
Subject: Re: [Geoserver-users] reconfiguring gewebcache for gda94
I think you forgot to tell us what the odd behaviour was?
I also note, from testing, that the geowebcache configuration shipped with
geoserver 2.0.2 was not quite working; Arne applied some patches in order to
get me a demo machine to test against.
Jody
On 22/08/2010, at 3:41 PM, Kolomeitz Shaun wrote:
Dear GeoServers,
I am seeing some very odd behaviour when trying to use a previously working
(but older) geowebcache.xml file in geoserver 2.0.2.
I have created a custom gridset to use EPSG:4283 (using a short gridset name
of GDA94) in geowebcache.xml.
<?xml version="1.0" encoding="utf-8"?>
<gwcConfiguration xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:noNamespaceSchemaLocation="http://geowebcache.org/schema/1.2.0/geowebcache.xsd"
xmlns="http://geowebcache.org/schema/1.2.0">
<version>1.2.0</version>
<backendTimeout>120</backendTimeout>
<gridSets>
<gridSet>
<name>GDA94</name>
<srs><number>4283</number></srs>
<extent><coords>
<double>137\.8125000</double><double>\-29\.5751949</double>
<double>154\.2041016</double><double>\-10\.3271480</double>
</coords></extent>
<alignTopLeft>true</alignTopLeft>
<levels>10</levels>
<metersPerUnit>111226.31</metersPerUnit>
<tileHeight>512</tileHeight>
<tileWidth>512</tileWidth>
</gridSet>
</gridSets>
<layers>
<wmsLayer><name>topp:telascience</name>
<gridSubsets><gridSubset><gridSetName>GDA94</gridSetName>
<zoomStart>0</zoomStart>
<zoomStop>9</zoomStop>
</gridSubset></gridSubsets>
<wmsUrl><string>http://localhost:8080/geoserver/wms</string></wmsUrl>
<wmsLayers>topp:telascience</wmsLayers>
</wmsLayer>
<wmsLayer><name>topp:100ktopo</name>
<gridSubsets><gridSubset><gridSetName>GDA94</gridSetName>
<zoomStart>0</zoomStart>
<zoomStop>9</zoomStop>
</gridSubset></gridSubsets>
<wmsUrl><string>http://localhost:8080/geoserver/wms</string></wmsUrl>
<wmsLayers>topp:100ktopo</wmsLayers>
</wmsLayer>
<wmsLayer><name>tiger:common_estate_label</name>
<gridSubsets><gridSubset><gridSetName>GDA94</gridSetName>
<zoomStart>0</zoomStart>
<zoomStop>9</zoomStop>
</gridSubset></gridSubsets>
<wmsUrl><string>http://localhost:8080/geoserver/wms</string></wmsUrl>
<wmsLayers>tiger:common_estate_label</wmsLayers>
</wmsLayer>
<wmsLayer><name>tiger:common_estate</name>
<gridSubsets><gridSubset><gridSetName>GDA94</gridSetName>
<zoomStart>0</zoomStart>
<zoomStop>9</zoomStop>
</gridSubset>
</gridSubsets>
<wmsUrl><string>http://localhost:8080/geoserver/wms</string></wmsUrl>
<wmsLayers>tiger:common_estate</wmsLayers>
</wmsLayer>
<wmsLayer><name>tiger:common_town</name>
<gridSubsets><gridSubset> <gridSetName>GDA94</gridSetName>
<zoomStart>0</zoomStart>
<zoomStop>9</zoomStop>
</gridSubset>
</gridSubsets>
<wmsUrl><string>http://localhost:8080/geoserver/wms</string></wmsUrl>
<wmsLayers>tiger:common_town</wmsLayers>
</wmsLayer>
</layers>
</gwcConfiguration>
This worked fine before upgrading to the current geoserver 2.0.2, except now
I see the following in the GWC demo page –
topp:100ktopo
Seed this layer
EPSG:4283_topp:100kt... OpenLayers: [png, gif, png8, jpeg]
EPSG:4326 OpenLayers: [png, gif, png8, jpeg] KML: [png, gif,
png8, jpeg, kml]
GDA94 OpenLayers: [png, gif, png8, jpeg]
EPSG:900913 OpenLayers: [png, gif, png8, jpeg]
Why has the EPSG:4283_topp:100kt… suddenly appeared when it is isn’t even
listed in geowebcache.xml ?
I am also now seeing an error appearing in the geoserver.log file that the
tilesize (512x512) does not match (256x256) ?
If I change the tilesize of course all the old tiles are now invalid and
will need to be reseeded or generated on the fly.
Does anyone in Aus have a more local example of geowebcache.xml for GDA94
and do I need to be more specific about other parameters now in the config
file ?
Many thanks,
Shaun
+----------------------------------------------------------------+
Think B4U Print
1 ream of paper = 6% of a tree and 5.4kg CO2 in the atmosphere
3 sheets of A4 paper = 1 litre of water
+----------------------------------------------------------------+
------------------------------------------------------------------------------
This SF.net email is sponsored by
Make an app they can't live without
Enter the BlackBerry Developer Challenge
Best Open Source Mac Front-Ends 2024
_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users
