I apologise in advance for posting so many follow ups to the list. I'm
hoping this will come to an end very soon.
I figured out that I need to place the geowebcache.xml file I made into the
"data_dir\gwc" folder. I am now getting cached tiles for the gridset that I
created.
The problem is that I haven't defined the gridset or wmslayer in the xml
file correctly for EPSG:3031. I don't know what values to set for
"<extent> <coords>" or "<resolutions>".
The result is that I am getting small snippets of tiles that load quickly
(i.e. have been cached), but look completely wrong.
Does someone here have any idea how I can find out what values to use in
the geowebcache.xml file for EPSG:3031?
I've attached my current xml file.
Thanks in advance
Regards,
Brendan
On Tue, Nov 29, 2011 at 1:00 PM, brendan barrett <shogun...@gmail.com>wrote:
> Ok, after a lot of reading, I think I may know where I may be going wrong.
>
> The layer that I am trying to load is in EPSG 3031 (polar stereographic).
> I would imagine that I need to define a gridset, and that I would need to
> create a geowebcache.xml file to put this gridset into.
>
> I created the geowebcache.xml file, and placed a dummy gridset into it. I
> then moved the xml file to "C:\Program Files (x86)\GeoServer
> 2.1.2\webapps\geoserver\WEB-INF". When I restart the server though, it says
> "Failed to find geowebcache.xml" in the console.
>
> Could anyone tell me where I need to place this xml file?
>
> I've pasted the contents of my file in the hopes that someone can point
> out any possible errors as well.
>
> 1. For "<extent><coords>", I used the "Projected Bounds" values from here:
> http://spatialreference.org/ref/epsg/3031/
> 2. I have no idea what to use for "<resolutions>", so I left those as I
> found them in the geowebcache.xml file I found lying around on the net.
>
> The contents of my file is as follows:
>
> <?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.2/geowebcache.xsd";
> xmlns="http://geowebcache.org/schema/1.2.2";>
>
> <!-- ============================== GLOBAL SETTINGS
> ======================================== -->
>
> <!-- The following controls certain automatic upgrades. Update this and
> the namespaces above when
> you update the configuration file manually -->
> <version>1.2.2</version>
> <!-- OPTIONAL This is the global timeout for HTTP connections to WMS
> backends. It is used both for the
> connection and the transfer, so the actual timeout may be much longer if
> the data is
> trickling back slowly. -->
> <backendTimeout>120</backendTimeout>
> <!-- OPTIONAL If the following is set to true you can append cached=false
> to requests and they will be
> proxied without caching. -->
> <cacheBypassAllowed>true</cacheBypassAllowed>
> <!-- OPTIONAL By default GWC displays simple runtime statistics on the
> front page -->
> <runtimeStats>true</runtimeStats>
>
>
> <!-- ============================== GRID SETS
> ============================================= -->
>
> <!-- OPTIONAL Grid Sets. If you do not define any here, the only ones
> available will be
> worldwide EPSG:4326 and EPSG:900913, in addition to any that are
> automatically
> generated for the GetCapabilities configuration -->
> <gridSets>
> <gridSet>
> <!-- REQUIRED The name should imply something about use, extent or SRS -->
> <name>Polar_Stereographic</name>
> <!-- REQUIRED The SRS used for WMS requests. This is all the fallback
> lookup
> method for services that do not specify the grid set. Currently only
> EPSG codes are allowed, so you specify the number.
> -->
> <srs><number>3031</number></srs>
> <!-- REQUIRED The bounding box for the grid set. See the Grid Set
> documentation
> regarding how this is interpreted and adjusted. You should set this to the
> maximum values for which the given SRS is valid, you will limit it with
> gridSubset elements further down -->
> <extent>
> <coords>
> <double>-0</double>
> <double>-3333134.0276</double>
> <double>0</double>
> <double>0</double>
> </coords>
> </extent>
> <tileHeight>512</tileHeight>
> <tileWidth>512</tileWidth>
> <resolutions>
> <double>1.40625</double>
> <double>0.703125</double>
> <double>0.3515625</double>
> <double>0.17578125</double>
> <double>0.087890625</double>
> <double>0.0439453125</double>
> <double>0.02197265625</double>
> <double>0.010986328125</double>
> <double>0.0054931640625</double>
> </resolutions>
>
> </gridSet>
> </gridSets>
> <wmsLayer>
> <!-- Layer details -->
> <name>LIMA</name>
> <wmsUrl><string>http://localhost:1024/geoserver/wms</string></wmsUrl>
> <gridSubset>
> <gridSetName>Polar_Stereographic</gridSetName>
> <!-- Eventuell extent -->
> </gridSubset>
> <!-- More layer details -->
> </wmsLayer>
>
> </gwcConfiguration>
>
>
>
>
>
>
> On Tue, Nov 29, 2011 at 11:32 AM, brendan barrett <shogun...@gmail.com>wrote:
>
>> I just realised I didn't reply to all, so the list wasn't getting my
>> emails... sorry.
>>
>> Would my data being in polar stererographic have anything to do with the
>> demos not displaying?
>>
>> On Tue, Nov 29, 2011 at 11:30 AM, brendan barrett <shogun...@gmail.com>wrote:
>>
>>> Hi Andrea
>>>
>>> Thanks for the response.
>>>
>>> When I go to that page, I try out the demo by clicking "jpeg" next to
>>> either the 4326 or 900913 options of the layer, but the page it takes me to
>>> remains blank... with no data. In the log file, I see the following
>>>
>>> "2011-11-29 11:27:43,086 INFO [geowebcache.GeoWebCacheDispatcher] - Read
>>> 425 from blank PNG file (expected 425)."
>>>
>>>
>>> On Tue, Nov 29, 2011 at 11:20 AM, Andrea Aime <
>>> andrea.a...@geo-solutions.it> wrote:
>>>
>>>> On Tue, Nov 29, 2011 at 8:27 AM, brendan barrett
>>>> <shogun...@gmail.com>wrote:
>>>>
>>>>> Hey
>>>>>
>>>>> What an awesome project. I've been battling for days to get a reliable
>>>>> WMS. Yesterday I downloaded Geoserver, install in a few minutes and
>>>>> after a little reading I am up and running. Unbelievable. Thanks to
>>>>> everyone that has been working on this project. I hope to be able to
>>>>> contribute to it moving forward.
>>>>>
>>>>> Now for a question:
>>>>> I am trying to enable tile caching, but everything I do doesn't seem
>>>>> to work.
>>>>>
>>>>> >From the beginning: I added a new WorkSpace, then added a Store (which
>>>>> feeds off a GeoTiff). I then published the layer. Under the
>>>>> GeoWebCache menu item, I checked "Enable direct WMS integration". I
>>>>> assume this means that when I do a layer preview (using "Tiled" not
>>>>> "Single tile"), that it should be adding tiles to the cache, and
>>>>> reading from that cache when I view parts of the map I have already
>>>>> viewed.
>>>>>
>>>>
>>>> Nope, it's not necessarily like that. The tiled view in the GeoServer
>>>> preview is not
>>>> setup to be aligned to the fixed tile grid that GWC uses, so it's not
>>>> going to
>>>> populate the tile cache directly.
>>>>
>>>> If you are using tiling you are better off using the GWC own demo
>>>> viewers, which
>>>> are setup to work against the fixed GWC tile structure instead:
>>>>
>>>> http://locahost:8080/geoserver/gwc/demo<http://demo1.geo-solutions.it/playground/gwc/demo>
>>>>
>>>> Cheers
>>>> Andrea
>>>>
>>>> --
>>>> -------------------------------------------------------
>>>> Ing. Andrea Aime
>>>> GeoSolutions S.A.S.
>>>> Tech lead
>>>>
>>>> Via Poggio alle Viti 1187
>>>> 55054 Massarosa (LU)
>>>> Italy
>>>>
>>>> phone: +39 0584 962313
>>>> fax: +39 0584 962313
>>>>
>>>> http://www.geo-solutions.it
>>>> http://geo-solutions.blogspot.com/
>>>> http://www.youtube.com/user/GeoSolutionsIT
>>>> http://www.linkedin.com/in/andreaaime
>>>> http://twitter.com/geowolf
>>>>
>>>> -------------------------------------------------------
>>>>
>>>
>>>
>>
>
<?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.2/geowebcache.xsd";
xmlns="http://geowebcache.org/schema/1.2.2";>
<!-- ============================== GLOBAL SETTINGS ======================================== -->
<!-- The following controls certain automatic upgrades. Update this and the namespaces above when
you update the configuration file manually -->
<version>1.2.2</version>
<!-- OPTIONAL This is the global timeout for HTTP connections to WMS backends. It is used both for the
connection and the transfer, so the actual timeout may be much longer if the data is
trickling back slowly. -->
<backendTimeout>120</backendTimeout>
<!-- OPTIONAL If the following is set to true you can append cached=false to requests and they will be
proxied without caching. -->
<cacheBypassAllowed>true</cacheBypassAllowed>
<!-- OPTIONAL By default GWC displays simple runtime statistics on the front page -->
<runtimeStats>true</runtimeStats>
<!-- ============================== GRID SETS ============================================= -->
<!-- OPTIONAL Grid Sets. If you do not define any here, the only ones available will be
worldwide EPSG:4326 and EPSG:900913, in addition to any that are automatically
generated for the GetCapabilities configuration -->
<gridSets>
<gridSet>
<!-- REQUIRED The name should imply something about use, extent or SRS -->
<name>EPSG:3031</name>
<!-- REQUIRED The SRS used for WMS requests. This is all the fallback lookup
method for services that do not specify the grid set. Currently only
EPSG codes are allowed, so you specify the number.
-->
<srs><number>3031</number></srs>
<!-- REQUIRED The bounding box for the grid set. See the Grid Set documentation
regarding how this is interpreted and adjusted. You should set this to the
maximum values for which the given SRS is valid, you will limit it with
gridSubset elements further down -->
<extent>
<coords>
<double>-250000</double>
<double>-250000</double>
<double>250000</double>
<double>250000</double>
</coords>
</extent>
<tileHeight>256</tileHeight>
<tileWidth>256</tileWidth>
<resolutions>
<double>1.40625</double>
<double>0.703125</double>
<double>0.3515625</double>
<double>0.17578125</double>
<double>0.087890625</double>
<double>0.0439453125</double>
<double>0.02197265625</double>
<double>0.010986328125</double>
<double>0.0054931640625</double>
</resolutions>
</gridSet>
</gridSets>
<layers>
<wmsLayer>
<!-- Layer details -->
<name>LIMAWMSLayer</name>
<gridSubsets>
<gridSubset>
<gridSetName>EPSG:3031</gridSetName>
</gridSubset>
</gridSubsets>
<grids>
<entry>
<srs>
<number>3031</number>
</srs>
<grid>
<srs>
<number>3031</number>
</srs>
<dataBounds>
<coords>
<double>-250000</double>
<double>-250000</double>
<double>250000</double>
<double>250000</double>
</coords>
</dataBounds>
<gridBounds>
<coords>
<double>-250000</double>
<double>-250000</double>
<double>250000</double>
<double>250000</double>
</coords>
</gridBounds>
</grid>
</entry>
</grids>
<wmsUrl><string>http://localhost:1024/geoserver/wms</string></wmsUrl>
<wmsLayers>Antarctica:LIMA</wmsLayers>
<!-- More layer details -->
</wmsLayer>
</layers>
</gwcConfiguration>------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure
contains a definitive record of customers, application performance,
security threats, fraudulent activity, and more. Splunk takes this
data and makes sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-novd2d
_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users
