[MapProxy] grid resolution configuration problem
Travis Kirstine
traviskirstine at gmail.com
Mon Oct 17 09:12:56 PDT 2022
one too many commas?
try changing 0.0076506024, # 19 25.00000000 to 0.0076506024 # 19
25.00000000 and remove the comma
On Mon, 17 Oct 2022 at 09:59, PONELLE, Luc <luc.ponelle at veolia.com> wrote:
> Hello
> We upgrade our mapproxy environnemnt with the 1.15.1 version
> When we launch mapproxy, we have the following error :
> 2022-10-17T11:10:38.243+02:00
> mounting /mapproxy-app.py on /mapproxy
> 2022-10-17T11:10:38.313+02:00
>
> [30602.4096385542, 15301.2048192771, 3060.2409638554, 1530.1204819277,
> 765.0602409639, 306.0240963855, 153.0120481928, 76.5060240964,
> 30.6024096386, 15.3012048193, 7.6506024096, 3.0602409639,
> 1.5301204819, 0.765060241, 0.3060240964, 0.1530120482, 0.0765060241,
> 0.0306024096, 0.0153012048, 0.0076506024] in grids.res not of type
> dict
> 2022-10-17T11:10:38.313+02:00invalid configuration
>
> The mapproxy.yaml resolution grids is configured like this :
>
> grids:
> epgs_3857:
> srs: EPSG:3857
> # Generated with:
> # % docker exec -ti dd15ada724d8 mapproxy-util scales --dpi 83
> --as-res-config 10000000 5000000 2500000 1000000 500000 250000 100000
> 50000 25000 10000 5000 2500 1000 500 250 100 50 25
> res: [
> # res level scale @83.0 DPI
> 30602.4096385542, # 0 100000000.00000000
> 15301.2048192771, # 1 50000000.00000000
> 3060.2409638554, # 2 10000000.00000000
> 1530.1204819277, # 3 5000000.00000000
> 765.0602409639, # 4 2500000.00000000
> 306.0240963855, # 5 1000000.00000000
> 153.0120481928, # 6 500000.00000000
> 76.5060240964, # 7 250000.00000000
> 30.6024096386, # 8 100000.00000000
> 15.3012048193, # 9 50000.00000000
> 7.6506024096, # 10 25000.00000000
> 3.0602409639, # 11 10000.00000000
> 1.5301204819, # 12 5000.00000000
> 0.7650602410, # 13 2500.00000000
> 0.3060240964, # 14 1000.00000000
> 0.1530120482, # 15 500.00000000
> 0.0765060241, # 16 250.00000000
> 0.0306024096, # 17 100.00000000
> 0.0153012048, # 18 50.00000000
> 0.0076506024, # 19 25.00000000
> ]
>
> Anybody has an idea to fix this problem ?
> THanks in advance
> Luc
>
> --
>
>
> --------------------------------------------------------------------------------------------This
>
> e-mail transmission (message and any attached files) may contain
> information that is proprietary, privileged and/or confidential to Veolia
> Environnement and/or its affiliates and is intended exclusively for the
> person(s) to whom it is addressed. If you are not the intended recipient,
> please notify the sender by return e-mail and delete all copies of this
> e-mail, including all attachments. Unless expressly authorized, any use,
> disclosure, publication, retransmission or dissemination of this e-mail
> and/or of its attachments is strictly prohibited.
>
>
> Ce message
> electronique et ses fichiers attaches sont strictement confidentiels et
> peuvent contenir des elements dont Veolia Environnement et/ou l'une de ses
> entites affiliees sont proprietaires. Ils sont donc destines a l'usage de
> leurs seuls destinataires. Si vous avez recu ce message par erreur, merci
> de le retourner a son emetteur et de le detruire ainsi que toutes les
> pieces attachees. L'utilisation, la divulgation, la publication, la
> distribution, ou la reproduction non expressement autorisees de ce message
> et de ses pieces attachees sont interdites.
>
> --------------------------------------------------------------------------------------------
> _______________________________________________
> MapProxy mailing list
> MapProxy at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/mapproxy
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/mapproxy/attachments/20221017/0eb67b7f/attachment.htm>
More information about the MapProxy
mailing list