GeoWebCache

Changes between Version 1 and Version 2 of Version1.2.2

Show
Ignore:
Timestamp:
03/02/10 20:57:35 (6 months ago)
Author:
arneke (IP: 80.202.77.128)
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Version1.2.2

    v1 v2  
    11'''!GeoWebCache 1.2.2 is out, get it [https://sourceforge.net/projects/geowebcache/files/ from SourceForge]''' 
    22 
    3 The driver behind this release was mainly a slight refactoring to make it easier to integrate GWC into !GeoServer, as you will see we have some improvements lined up for GS 2.0.1. But a number of minor fixes and improvements have also made it into this release. 
     3In addition to the new features below, 1.2.2 introduces Gabriel Roldan as a new core developer. Gabriel has been a part of the GeoServer / GeoTools community for several years and brings loads of experience to the project. His first contribution  
    44 
    5 The configuration file has been expanded, but the upgrade should be automatic from 1.2.0 or 1.2.1. The metastore database is not changed by this release. 
     5The metastore database is not changed by this release, but backing up your database is recommended regardless. 
    66 
    77'''New features''' 
    88 
    9 GeoWebCache 1.2.2 can now answer regular WMS requests. The limitation is mainly that it cannot reproject, recombining tiles and resampling the resulting raster works well and response times as generally less than a second. PNG is used as the input format. 
     9Thanks to Geomatics and Cartographic Research Centre  at Carlon Universit (Amos Hayes), GeoWebCache 1.2.2 can now answer regular WMS requests. The (intentional) limitation is mainly that it cannot reproject, so the layer must be configured for the SRS that you wish to serve. Recombining tiles and resampling the resulting raster works well and response times as generally less than a second. However, you should make sure that the steps between resolutions are not too great, otherwise very large canvases will have to be created in memory. PNG tiles are used as the input, so the layer must be configured to support this format. Line art and text tend to suffer when resampling the image, though in future versions it may be possible to adjust the interpolation used to lessen this problem. 
    1010 
    11 Also, OSGeo TMS (Tile Map Service) is now supported with the XML documents. All formats and projections are supported, using a a conventions of <Layer Name>@<Grid Set Id>@<format extension>. However, requests depending on the old convention, which relied on the default SRS and format, should still work. 
     11OSGeo TMS (Tile Map Service) is now supported with the XML documents. All formats and projections are supported, using a a conventions of <Layer Name>@<Grid Set Id>@<format extension>. However, requests depending on the old convention, which relied on the default SRS and format, should still work. 
    1212 
    13 Minimal meta data for layers is now supported. You can set title and description on layers. These values will also be picked up automatically for layers configured from a getcapabilities document. 
     13GeoRSS support. GeoWebCache can now expire tiles based on a GeoRSS GML feed. The feed should contain GML describing all features that have changed. If a feature shrinks or moves, be sure to also include the old ou. In addition to the GeoRSS GML specification, GWC supports MultiPolygons. See the exhaustive example in the documentation.  
     14 
     15Minimal meta data for layers is now supported. You can set the title and description on layers. These values will also be picked up automatically for layers configured from a getcapabilities document. 
    1416 
    1517 
     
    1820#121 During the 1.2.0 refactor the format test was moved out of the service objects, but not committed to the layer objects. As a result, clients could request valid formats that the layer was not intentionally configured for. None of the capability documents advertised this. The ticket contains instructions for cleaning up any undesired tiles on disk. 
    1921 
     22There have been several reports about problems with the expireCacheList directive, but these were not reproducible on trunk at the time. We will revisit them if anyone still encounters problems with 1.2.2. 
     23 
     24GeoServer had switched back to making "download" the default mode for KML, breaking GWC caching which assumed regionated tiles. GWC will now append the necessary string to all requests. 
     25 
     26The Reload functionality appears to have been broken in 1.2.1. Thanks to Surendran for reporting. 
     27 
    2028'''Exciting stuff lined up for 1.2.3, or 1.3.0:''' 
    2129 
    22 The LRU functionality (to set a fixed size limit on layers) did not quiet make it into 1.2.2. We therefore plan to get this into 1.2.3. However, GeoWebCache has also gotten to the point that it needs to be cut into several modules. A first attempt will be made at the TOPP NYC Sprint 2010. 
     30The LRU (Least-Recently-Used) functionality (to set a fixed size limit on layers) did not quiet make it into 1.2.2. So this should get into 1.2.3. However, GeoWebCache has also gotten to the point that it needs to be cut into several modules. This was discussed at the NYC Sprint 2010 at the end of February, we will see where it takes us.