<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:Calibri
}
--></style></head>
<body class='hmmessage'><div dir='ltr'>Hi list<BR>I have a mapproxy setup that runs behind apache2.2 server in a Windows environment. I have a large cache ~140gb stored in a file structure. <BR>I demo site workes fine but I can see that as I get the higher zoom levels I see that the map is much slower at loading tiles, but once the tiles are loaded for the first time panning seems to work fine but I notice the same drop in preformance when I zoom in Again. I guess this has something to do with the cache size and the Windows abitly to index extremely large numbers of folders and images. Has anyone else experienced this? could a solution be to transfore the cache to sqllite databases? and if so what are the preformance conciderations of doing this?. I might be worth noting that the preformance drop is within the cached area / zoom depth.<br> <BR><div>> From: mapproxy-request@lists.osgeo.org<br>> Subject: MapProxy Digest, Vol 46, Issue 3<br>> To: mapproxy@lists.osgeo.org<br>> Date: Wed, 11 Dec 2013 12:00:06 -0800<br>> <br>> Send MapProxy mailing list submissions to<br>> mapproxy@lists.osgeo.org<br>> <br>> To subscribe or unsubscribe via the World Wide Web, visit<br>> http://lists.osgeo.org/mailman/listinfo/mapproxy<br>> or, via email, send a message with subject or body 'help' to<br>> mapproxy-request@lists.osgeo.org<br>> <br>> You can reach the person managing the list at<br>> mapproxy-owner@lists.osgeo.org<br>> <br>> When replying, please edit your Subject line so it is more specific<br>> than "Re: Contents of MapProxy digest..."<br>> <br>> <br>> Today's Topics:<br>> <br>> 1. Re: Space in Layername (J?ger)<br>> 2. Re: Space in Layername (Rahkonen Jukka)<br>> 3. Re: Space in Layername (Oliver Tonnhofer)<br>> <br>> <br>> ----------------------------------------------------------------------<br>> <br>> Message: 1<br>> Date: Wed, 11 Dec 2013 12:54:01 +0000<br>> From: J?ger, Frank (KRZ) <F.Jaeger@KRZ.DE><br>> To: "'mapproxy@lists.osgeo.org'" <mapproxy@lists.osgeo.org><br>> Subject: Re: [MapProxy] Space in Layername<br>> Message-ID: <F2176AE4E9FFAF45BEA8D84DD6F4AF1A0C3E038F@skrzmxmbx02><br>> Content-Type: text/plain; charset="iso-8859-1"<br>> <br>> > -----Urspr?ngliche Nachricht-----<br>> > Von: Oliver Tonnhofer [mailto:olt@omniscale.de]<br>> > Betreff: Re: [MapProxy] Space in Layername<br>> <br>> <br>> > On 10.12.2013, at 15:00, J?ger, Frank (KRZ) wrote:<br>> > > YAML: How to code a Space in the layername?<br>> > > sources: ["wms_src:the layer"]<br>> > <br>> > That should work. I tested it with MapProxy 1.6 and it made requests with<br>> > proper URL encoding (i.e. "&layers=the+layer").<br>> > What URL do you see in the source requests logs or serve-develop output)?<br>> > <br>> > Regards,<br>> > Oliver<br>> <br>> Maybe the problem is the WMS-Server. It's an ArcGIS 9 and - no - it's not under my control.<br>> <br>> GetMap says: "Could not get any sources: no image returned from source WMS"<br>> <br>> wms Feature Info answers: <br>> <br>> <ServiceException code="LayerNotDefined"><br>> Parameter 'layer(s)' contains unacceptable value: Umringe+Kreis<br>> </ServiceException><br>> <br>> The '+' is there but has to be removed on servers side to fit the Layer-Name.<br>> <br>> Frank<br>> -------------- next part --------------<br>> A non-text attachment was scrubbed...<br>> Name: smime.p7s<br>> Type: application/pkcs7-signature<br>> Size: 7618 bytes<br>> Desc: not available<br>> URL: <http://lists.osgeo.org/pipermail/mapproxy/attachments/20131211/c191e2e0/attachment-0001.bin><br>> <br>> ------------------------------<br>> <br>> Message: 2<br>> Date: Wed, 11 Dec 2013 13:32:41 +0000<br>> From: Rahkonen Jukka <jukka.rahkonen@mmmtike.fi><br>> To: 'J?ger, Frank (KRZ)' <F.Jaeger@KRZ.DE>,<br>> "'mapproxy@lists.osgeo.org'" <mapproxy@lists.osgeo.org><br>> Subject: Re: [MapProxy] Space in Layername<br>> Message-ID:<br>> <84446DEF76453C439E9E97E438E13A631F0A6F2B@suutari.haapa.mmm.fi><br>> Content-Type: text/plain; charset="iso-8859-1"<br>> <br>> Hi,<br>> <br>> I fear I was wrong with the acceptable layer names.<br>> <br>> Typename in WFS 1.0.0 and 1.1.0 is of type QName and does not allow spaces<br>> http://schemas.opengis.net/wfs/1.0.0/WFS-basic.xsd<br>> However, layer names in WMS are of type string and spaces are OK<br>> http://schemas.opengis.net/wms/1.3.0/capabilities_1_3_0.xsd<br>> <br>> I have thought for years that OGC standards behave similarly with layer names and typenames but obviously they do not.<br>> <br>> Thus ArcGIS server has acceptable layer names and the trouble is only in how to make MapProxy to pass them correctly. I hope this Mapserver thread gives some ideas for you. <br>> <br>> http://osgeo-org.1560.x6.nabble.com/cascading-wms-and-layer-names-encoding-td5058504.html<br>> <br>> <br>> -Jukka Rahkonen-<br>> <br>> <br>> J?ger, Frank (KRZ) wrote:<br>> <br>> > <br>> > > -----Urspr?ngliche Nachricht-----<br>> > > Von: Oliver Tonnhofer [mailto:olt@omniscale.de]<br>> > > Betreff: Re: [MapProxy] Space in Layername<br>> > <br>> > <br>> > > On 10.12.2013, at 15:00, J?ger, Frank (KRZ) wrote:<br>> > > > YAML: How to code a Space in the layername?<br>> > > > sources: ["wms_src:the layer"]<br>> > ><br>> > > That should work. I tested it with MapProxy 1.6 and it made requests<br>> > > with proper URL encoding (i.e. "&layers=the+layer").<br>> > > What URL do you see in the source requests logs or serve-develop output)?<br>> > ><br>> > > Regards,<br>> > > Oliver<br>> > <br>> > Maybe the problem is the WMS-Server. It's an ArcGIS 9 and - no - it's not under<br>> > my control.<br>> > <br>> > GetMap says: "Could not get any sources: no image returned from source WMS"<br>> > <br>> > wms Feature Info answers:<br>> > <br>> > <ServiceException code="LayerNotDefined"> Parameter 'layer(s)' contains<br>> > unacceptable value: Umringe+Kreis </ServiceException><br>> > <br>> > The '+' is there but has to be removed on servers side to fit the Layer-Name.<br>> > <br>> > Frank<br>> <br>> <br>> ------------------------------<br>> <br>> Message: 3<br>> Date: Wed, 11 Dec 2013 15:52:19 +0100<br>> From: Oliver Tonnhofer <olt@omniscale.de><br>> To: Rahkonen Jukka <Jukka.Rahkonen@mmmtike.fi><br>> Cc: "'mapproxy@lists.osgeo.org'" <mapproxy@lists.osgeo.org><br>> Subject: Re: [MapProxy] Space in Layername<br>> Message-ID: <FB694CDD-0779-4846-B65E-14C5EA9B2283@omniscale.de><br>> Content-Type: text/plain; charset=windows-1252<br>> <br>> <br>> On 11.12.2013, at 14:32, Rahkonen Jukka wrote:<br>> > I fear I was wrong with the acceptable layer names.<br>> > <br>> > Typename in WFS 1.0.0 and 1.1.0 is of type QName and does not allow spaces<br>> > http://schemas.opengis.net/wfs/1.0.0/WFS-basic.xsd<br>> > However, layer names in WMS are of type string and spaces are OK<br>> > http://schemas.opengis.net/wms/1.3.0/capabilities_1_3_0.xsd<br>> > <br>> > I have thought for years that OGC standards behave similarly with layer names and typenames but obviously they do not.<br>> <br>> Yeah, unfortunately the OGC only mentions "machine readable" and a programmer automatically thinks of identifiers as in variable/function names (alphanumerical with underscore), but the spec does not restrict the name to any characters.<br>> <br>> <br>> > Thus ArcGIS server has acceptable layer names and the trouble is only in how to make MapProxy to pass them correctly. I hope this Mapserver thread gives some ideas for you. <br>> <br>> I do think that MapProxy handles this right. But I might be wrong.<br>> <br>> WMS query parameters are sent in an HTTP GET request as application/x-www-form-urlencoded data and this defines that spaces should be encoded as "+". WMS 1.1.0 clearly stated that ```[...] the space character (" ") is an exception, and shall be encoded as a plus sign ("+"). A server shall be prepared to decode any character encoded in this manner.```<br>> WMS 1.1.1 only refers to the RFC 2396, but this RFC does not define the encoding of the query part. <br>> WMS 1.3.0 made it clear again that "The server shall be prepared to decode any character escaped in this manner, and to decode the ?+? character as a space."<br>> <br>> So ArcGIS should handle a request for `...&layers=Umringe+Kreis&...` as a request for the layer "Umringe Kreis".<br>> <br>> <br>> > http://osgeo-org.1560.x6.nabble.com/cascading-wms-and-layer-names-encoding-td5058504.html<br>> <br>> <br>> Form the last mail:<br>> <br>> > <br>> > 2) mapfile encoding the layers list works fine<br>> > [...]<br>> > the original wms server logs this (iis):<br>> > <br>> > LAYERS=Albufeiras%25201ria%2cRegadio%2520EFMA%2520simples%2cAdu%25C3%25A7%25C3%25A3o%2520simples<br>> <br>> <br>> This looks like it's encoded twice. It's hard to believe that IIS/ArcGIS are really expecting that and I don't know where they could have interpreted that in the spec. Any ArcGIS experts around?<br>> <br>> <br>> Regards,<br>> Oliver<br>> <br>> -- <br>> Oliver Tonnhofer | Omniscale GmbH & Co KG | http://omniscale.com<br>> http://mapproxy.org | https://github.com/olt | @oltonn<br>> <br>> <br>> <br>> <br>> <br>> <br>> <br>> <br>> <br>> ------------------------------<br>> <br>> _______________________________________________<br>> MapProxy mailing list<br>> MapProxy@lists.osgeo.org<br>> http://lists.osgeo.org/mailman/listinfo/mapproxy<br>> <br>> End of MapProxy Digest, Vol 46, Issue 3<br>> ***************************************<br></div> </div></body>
</html>