Hi Gabriel,
The geowebcache.xml is working right now, it really was an issue with the xml. When I added the <layers> element everything worked well. Thanks a lot for your help!! I encountered something different but will post this with a new subject. Cheers Torsten -------------------------------------------------------------------------- T-Systems International GmbH Torsten Drey Spezialist Geo-Consulting GeoServices/GIS Vorgebirgsstraße 49 D-53119 Bonn Fon: +49 (0)228 9841 3690 Fax: +49 (0)228 9841 3990 E-Mail: [email protected] Internet: http://www.t-systems.com T-Systems International GmbH Aufsichtsrat: René Obermann (Vorsitzender) Geschäftsführung: Reinhard Clemens (Vorsitzender), Dr. Ferri Abolhassan, Olaf Heyden, Georg Pepping, Klaus Werner Handelsregister: Amtsgericht Frankfurt am Main HRB 55933 Sitz der Gesellschaft: Frankfurt am Main WEEE-Reg.-Nr. DE87523644 Notice: This transmittal and/or attachments may be privileged or confidential. If you are not the intended recipient, you are hereby notified that you have received this transmittal in error; any review, dissemination, or copying is strictly prohibited. If you received this transmittal in error, please notify us immediately by reply and immediately delete this message and all its attachments. Thank you. -----Ursprüngliche Nachricht----- Von: Drey, Torsten Gesendet: Mittwoch, 13. April 2011 08:45 An: 'Gabriel Roldán' Cc: [email protected] Betreff: AW: geowebcache.xml for different EPSG Hi Gabriel, do I understand this correctly: The layer in geowebcache.xml must have a different name. So how does GWC know for which layer the EPSG is set? I tried that, i.e., give the layer in geowebcache.xml a different name, but then Geoserver does not start at all after restarting tomcat or trying to start it manually. Could it be a problem with the xml? If I don't put the geowebcache.xml in data_dir/gwc I get the following error from catalina: ERROR [layer.TileLayerDispatcher] - Error reading service information from /appl/local/tomcat/5.5.25/webapps/Geoserver/../resources: Error parsing file /appl/local/tomcat/5.5.25/webapps/Geoserver/../resources/geowebcache.xml This leaves me puzzling as it looks as if Geoserver is looking for the geowebcache.xml in a 'resources' folder which I don't have. I thought it had to be put in 'gwc'. Do you know where I should put it? Is the configuration of a new EPSG generally supposed to work out with Geoserver 2.1 RC3? I would rather like to use a more stable version than switching to a nightly build as everything else (apart from the GWC) is running quite well. If it is not possible than I will give it a try and switch versions. Thanks a lot, cheers Torsten -------------------------------------------------------------------------- T-Systems International GmbH Torsten Drey Spezialist Geo-Consulting GeoServices/GIS Vorgebirgsstraße 49 D-53119 Bonn Fon: +49 (0)228 9841 3690 Fax: +49 (0)228 9841 3990 E-Mail: [email protected] Internet: http://www.t-systems.com T-Systems International GmbH Aufsichtsrat: René Obermann (Vorsitzender) Geschäftsführung: Reinhard Clemens (Vorsitzender), Dr. Ferri Abolhassan, Olaf Heyden, Georg Pepping, Klaus Werner Handelsregister: Amtsgericht Frankfurt am Main HRB 55933 Sitz der Gesellschaft: Frankfurt am Main WEEE-Reg.-Nr. DE87523644 Notice: This transmittal and/or attachments may be privileged or confidential. If you are not the intended recipient, you are hereby notified that you have received this transmittal in error; any review, dissemination, or copying is strictly prohibited. If you received this transmittal in error, please notify us immediately by reply and immediately delete this message and all its attachments. Thank you. -----Ursprüngliche Nachricht----- Von: Gabriel Roldan [mailto:[email protected]] Im Auftrag von Gabriel Roldán Gesendet: Dienstag, 12. April 2011 17:43 An: Drey, Torsten Cc: [email protected] Betreff: Re: [Geoserver-users] geowebcache.xml for different EPSG make sure you name the layer in geowebcache.xml different than the one in GeoServer or it won't be found. OR: try the following with a 2.2-SNAPSHOT nightly build, define only the gridset in geowebcache.xml, and then go and hand edit the file <data dir>/workspaces/<workspace>/<data store>/<feature type>/layer.xml and set the following metadata property: <metadata> <entry key="GWC.gridSets">EPSG:4326,EPSG:900913,EPSG:32632</entry> </metadata> Sorry it is not yet possible to set that value through the user interface yet. That kind of integration is work in progress, so it'd be great if you can try that and tell if it worked as expected. Cheers, Gabriel On Tue, 2011-04-12 at 12:06 +0200, [email protected] wrote: > Hi, > > I would like to use the integrated GeoWebCache with Geoserver but > failed so far in configuring the geowebcache.xml for a different EPSG > than the default ones. I would need to configure the geowebcache.xml > in such a way that also EPSG 32632, i.e. UTM Zone 32 N is supported. > Here is what I did so far: - I set the data_dir in WEB-INF/web.xml as > I use Geoserver 2.1RC3 with Tomcat - I made a gwc-dir in the data_dir > and put the geowebcache.xml inside it (see below) - Restartet > Geoserver, but the new EPSG is not showing up. Catalina.out says that > the geowebcache.xml could not be found. Where do I have to put it? > > Would be great if someone could help or point me in the right direction. > > Thanks > Torsten > > The geowebcache.xml looks like this: > ______________________________________________________________________ > _____________________________________________ > <?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>UTM_WGS84_Zone32</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>32632</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>166021</double> > <double>833000</double> > <double>9328000</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>fra:dtk25_200_addo</name> > > <wmsUrl><string>http://dxco01.gdc-bonn02.t-systems.com:8090/geoserver/wms</string></wmsUrl> > <gridSubset> > <gridSetName>UTM_WGS84_Zone32</gridSetName> > <!-- Eventuell extent --> > </gridSubset> > <!-- More layer details --> > </wmsLayer> > > </gwcConfiguration> > ______________________________________________________________ > > ---------------------------------------------------------------------- > ---- > T-Systems International GmbH > Torsten Drey > Spezialist Geo-Consulting > GeoServices/GIS > Vorgebirgsstraße 49 > D-53119 Bonn > > Fon: +49 (0)228 9841 3690 > Fax: +49 (0)228 9841 3990 > E-Mail: [email protected] > > Internet: http://www.t-systems.com > > T-Systems International GmbH > Aufsichtsrat: René Obermann (Vorsitzender) > Geschäftsführung: Reinhard Clemens (Vorsitzender), Dr. Ferri > Abolhassan, Olaf Heyden, Georg Pepping, Klaus Werner > Handelsregister: Amtsgericht Frankfurt am Main HRB 55933 Sitz der > Gesellschaft: Frankfurt am Main WEEE-Reg.-Nr. DE87523644 > > Notice: This transmittal and/or attachments may be privileged or > confidential. If you are not the intended recipient, you are hereby notified > that you have received this transmittal in error; any review, dissemination, > or copying is strictly prohibited. If you received this transmittal in error, > please notify us immediately by reply and immediately delete this message and > all its attachments. Thank you. > > ---------------------------------------------------------------------- > -------- Forrester Wave Report - Recovery time is now measured in > hours and minutes not days. Key insights are discussed in the 2010 > Forrester Wave Report as part of an in-depth evaluation of disaster > recovery service providers. > Forrester found the best-in-class provider in terms of services and vision. > Read this report now! http://p.sf.net/sfu/ibm-webcastpromo > _______________________________________________ > Geoserver-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/geoserver-users -- Gabriel Roldan [email protected] Expert service straight from the developers ------------------------------------------------------------------------------ Benefiting from Server Virtualization: Beyond Initial Workload Consolidation -- Increasing the use of server virtualization is a top priority.Virtualization can reduce costs, simplify management, and improve application availability and disaster protection. Learn more about boosting the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev _______________________________________________ Geoserver-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-users
