[MapProxy] Problem with custom projections

[Guillaume Sueur]

got it : in grid.py, line 80, default bbox for 4326 shouldn't use -90 
and 90 but -89.9999 and +89.9999

hope that helps

guillaume

Le 17/12/10 10:35, Guillaume Sueur a écrit :
>
>
> Le 17/12/10 10:30, Oliver Tonnhofer a écrit :
>>
>> On 16.12.2010, at 17:01, Guillaume Sueur wrote:
>>> Here it is.
>>> I was surprised to see a whole world extent instead of my grid extent.
>>
>> MapProxy merges all bounding boxes of your sources/caches and since
>> you are using the GLOBAL_XXXX grid definitions you will also get a
>> global BBOX in the capabilities.
>>
>> You need to remove the GLOBAL_XXXX grids from your configuration. The
>> next release will improve here: It will always show the actual BBOX of
>> your source if you are using the coverage feature.
>
> sounds good
>
>>
>> I hope that also answers your other mail.
>
> indeed. But we could think about adding bbox to the layer level.
>
>>
>>> Anyway, I think in case bbox goes to default EPSG:4326 values, it
>>> should then be -180,-89,180,89
>>
>> The BBOX is used to calculate the grid, so I can't just change that.
>> Can you check if it works with 89.99999999? I could then "round" the
>> values down in the capabilities for EPSG:4326.
>
> That bbox is nowhere in the maproxy.yaml. Where does MapProxy set the
> bbox for GLOBAL grids ? That's where the problem come from.
>
> Thanks for your assistance
>
> Guillaume
>
>
>>
>>
>> Regards,
>> Oliver
>>
> _______________________________________________
> MapProxy mailing list
> MapProxy at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/mapproxy
>