<div>Hi Oliver,</div><div><br></div>I'm running tip so not sure if this is in this release but I believe in mapproxy/config/spec.py <font class="Apple-style-span" face="'courier new', monospace">grids.anything().num_levels</font> should be <font class="Apple-style-span" face="'courier new', monospace">int() </font>instead of <font class="Apple-style-span" face="'courier new', monospace">str()</font> - I was running into exceptions loading configs (haven't run test suite).<div>
<br></div><div>Cheers,<br>Adon<br><br><div class="gmail_quote">On 19 May 2011 17:06, Oliver Tonnhofer <span dir="ltr"><<a href="mailto:olt@omniscale.de">olt@omniscale.de</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Hi there,<br>
<br>
it's time for a second beta release with some nice additions!<br>
<br>
The latest release is available at:<br>
<a href="http://mapproxy.org/static/rel/MapProxy-1.1.0b2.tar.gz" target="_blank">http://mapproxy.org/static/rel/MapProxy-1.1.0b2.tar.gz</a><br>
<br>
To update within you virtualenv:<br>
<br>
$ pip install <a href="http://mapproxy.org/static/rel/MapProxy-1.1.0b2.tar.gz" target="_blank">http://mapproxy.org/static/rel/MapProxy-1.1.0b2.tar.gz</a><br>
<br>
The current documentation is available at:<br>
<a href="http://mapproxy.org/docs/nightly/" target="_blank">http://mapproxy.org/docs/nightly/</a><br>
<br>
For a complete list of changes see:<br>
<a href="http://bitbucket.org/olt/mapproxy/src/1.1.0b2/CHANGES.txt" target="_blank">http://bitbucket.org/olt/mapproxy/src/1.1.0b2/CHANGES.txt</a><br>
<br>
<br>
Changes since 1.1.0b1:<br>
<br>
Improved logging<br>
----------------<br>
<br>
The logging was improved and unified. System information is now logged at<br>
``mapproxy.system``, configuration errors at ``mapproxy.config`` and all<br>
source errors under ``mapproxy.source.wms``, etc.<br>
<br>
All requests that MapProxy makes are now logged to<br>
``mapproxy.source.request``. The request log format changed and it now<br>
contains the complete URL (easy to copy&paste), the size and the duration<br>
of the request. The log contains also requests to non-HTTP sources like<br>
Mapnik or Mapserver.<br>
<br>
- <a href="http://mapproxy.org/docs/nightly/deployment.html#logging" target="_blank">http://mapproxy.org/docs/nightly/deployment.html#logging</a><br>
<br>
Improved configuration loading<br>
------------------------------<br>
<br>
The configuration loading is now more robust. You shouldn't see any stack<br>
traces when your configuration contains any syntax errors. The MapProxy<br>
and the seed configurations are now validated and you should see detailed<br>
information about missing or unknown options.<br>
<br>
We hope that we didn't miss any options. Please report if you still see<br>
any errors for a documented configuration option.<br>
<br>
Cache location<br>
--------------<br>
<br>
The default location of the cache will change with 1.2. The current<br>
default is ``../var/cache_dir`` which is appropriate for the configuration<br>
from ``paster create``, but not for the configuration from ``mapproxy-util<br>
create`` (see below). You should configure ``globals.cache.base_dir`` with<br>
your cache directory. Until then you will get a FutureWarning during<br>
startup.<br>
<br>
Some new features since 1.0:<br>
<br>
New sources<br>
-----------<br>
<br>
There are two new sources that directly integrate Mapserver and Mapnik<br>
into MapProxy. There is no need to setup an extra WMS server for these map<br>
services.<br>
<br>
- <a href="http://mapproxy.org/docs/nightly/sources.html#mapserver-label" target="_blank">http://mapproxy.org/docs/nightly/sources.html#mapserver-label</a><br>
- <a href="http://mapproxy.org/docs/nightly/sources.html#mapnik-label" target="_blank">http://mapproxy.org/docs/nightly/sources.html#mapnik-label</a><br>
<br>
The tile source was extended by the ``arcgiscache_path`` and ``bbox``<br>
parameters. ``arcgiscache_path`` allows the integration of existing ArcGIS<br>
tile caches (L09/R05397fb1/C0012d687) and the ``bbox`` parameter is useful<br>
for WMS-C services that expect a fixed parameter order.<br>
<br>
- <a href="http://mapproxy.org/docs/nightly/sources.html#url" target="_blank">http://mapproxy.org/docs/nightly/sources.html#url</a><br>
<br>
Tagged WMS Sources<br>
------------------<br>
<br>
You can tag WMS source names with layer names. It is no longer required to<br>
specify a WMS source multiple times, for each layer combination you use.<br>
You can now define a WMS once without any layers and then tag the source<br>
name with the layers you need.<br>
<br>
sources:<br>
wms1:<br>
type: wms<br>
req:<br>
url: <a href="http://example.org/service" target="_blank">http://example.org/service</a>?<br>
<br>
caches:<br>
mycache1:<br>
sources: [wms1:lyr1,lyr2]<br>
grids: [mygrid]<br>
mycache2:<br>
sources: [wms1:lyr3,lyr4]<br>
grids: [mygrid]<br>
<br>
- <a href="http://mapproxy.org/docs/nightly/sources.html#tagged-source-names" target="_blank">http://mapproxy.org/docs/nightly/sources.html#tagged-source-names</a><br>
<br>
Configurable Image Formats<br>
--------------------------<br>
<br>
Image formats are now much more flexible. You can now create custom image<br>
formats and modify them for each source or cache individually. The<br>
configuration of paletted PNGs or the JPEG quality is no longer a global<br>
option.<br>
<br>
- <a href="http://mapproxy.org/docs/nightly/configuration.html#image-format-options" target="_blank">http://mapproxy.org/docs/nightly/configuration.html#image-format-options</a><br>
<br>
There is now also support for integer images, e.g. for DEMs.<br>
<br>
WMTS<br>
----<br>
<br>
There is first support for the OGC WMTS standard. It implements KVP<br>
requests and can be used with existing caches.<br>
<br>
- <a href="http://mapproxy.org/docs/nightly/services.html#web-map-tile-services" target="_blank">http://mapproxy.org/docs/nightly/services.html#web-map-tile-services</a><br>
<br>
<br>
New mapproxy-util command line tool<br>
-----------------------------------<br>
<br>
There is a new mapproxy-util command that replaces the paster command for<br>
running the development server. You can now start a test server with:<br>
<br>
mapproxy-util serve-develop mapproxy.yaml<br>
<br>
Paster (PasteDeploy/PasteScript) is no longer a requirement, but it is<br>
still supported.<br>
<br>
- <a href="http://mapproxy.org/docs/nightly/deployment.html" target="_blank">http://mapproxy.org/docs/nightly/deployment.html</a><br>
<br>
<br>
Regards,<br>
Oliver<br>
<br>
--<br>
Oliver Tonnhofer | Omniscale GmbH & Co KG | <a href="http://omniscale.de" target="_blank">http://omniscale.de</a><br>
<a href="http://mapproxy.org" target="_blank">http://mapproxy.org</a> | <a href="https://bitbucket.org/olt" target="_blank">https://bitbucket.org/olt</a> | @oltonn<br>
<br>
<br>
<br>
<br>
_______________________________________________<br>
MapProxy mailing list<br>
<a href="mailto:MapProxy@lists.osgeo.org">MapProxy@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/mapproxy" target="_blank">http://lists.osgeo.org/mailman/listinfo/mapproxy</a><br>
</blockquote></div><br><br clear="all"><br>-- <br>Adon Metcalfe<br>Labyrinth Data Services Pty Ltd<br><a href="http://www.labyrinthdata.net.au">http://www.labyrinthdata.net.au</a><br>
</div>