[MapProxy] Custom grid, bbox problems and no GETs

Oliver Tonnhofer olt at omniscale.de
Fri Feb 19 03:21:23 PST 2016


Hi,

you need to use a bounding box that matches with the TopLeftCorner.
Your calculation (question 0) looks right, but you might need to switch x and y.


Q1: Additional buffers? It might use the LatLongBoundingBox?

You should remove all coverages, if the bbox is right and if you are still not seeing any requests.


Regards,
Oliver

-- 
Oliver Tonnhofer  | Omniscale GmbH & Co KG  | http://omniscale.com
OpenStreetMap WMS and tile services         | http://maps.omniscale.com



> On 17.02.2016, at 14:53, Starck Heinrich <Heinrich.Starck at energieag.at> wrote:
> 
>  
> Hello,
>  
> I still try to access to a public wmts offer
> http://srv.doris.at/arcgis/rest/services/Basisdaten/FlaeWi/MapServer/WMTS/1.0.0/WMTSCapabilities.xml
> In QGis I can access the WMTS offer.
>  
>  
> In the WMTSCapabilities.xml I see different grid/bbox definitions:
> 1.
> <ows:BoundingBox crs="urn:ogc:def:crs:EPSG::31255">
>          EPSG:31255 - bounding box:  -115771.3204, 130037.7189, 115359.4571, 408002.5351
>          (see http://spatialreference.org/ref/epsg/31255/)
> 2.
> <ows:BoundingBox crs="urn:ogc:def:crs:EPSG::31255">
>          <ows:LowerCorner>-4624770.696 -348480.1199000002</ows:LowerCorner>
>          <ows:UpperCorner>403981.5399999991 123233.68599999989</ows:UpperCorner>
> </ows:BoundingBox>
> 3.
> <TileMatrix>
>          <ows:Identifier>0</ows:Identifier>
>          <ScaleDenominator>2267861.678580215</ScaleDenominator>
>          <TopLeftCorner>5001000.0 -5622500.0</TopLeftCorner>
>          <TileWidth>256</TileWidth>
>          <TileHeight>256</TileHeight>
>          <MatrixWidth>36</MatrixWidth>
>          <MatrixHeight>60</MatrixHeight>
> </TileMatrix>
> ...
> <TileMatrixSet>default028mm</TileMatrixSet>
> ...
> x2: 5001000.0 + 256*0.28/1000.0*2267861.678580215*36  (correct?) <--- Question 0
> y2: -5622500.0 + 256*0.28/1000.0*2267861.678580215*60
>  
>  
> I tried to build an empty grid to see the bounding box (QGis):
>   test_grid_cache:
>     grids: [doris_flaewi_wmts_test_grid]
>     sources: []
>    
>   doris_flaewi_wmts_test_grid:
>     srs: 'EPSG:31255'
>     origin: 'nw'
>     bbox: [-115771.3204, 130037.7189, 115359.4571, 408002.5351]
>  
> In QGis (with 'polygon from layer extent') I get a different polygon/box. Why?   <--- Question 1
>  
> I add the x/y-differences and justify the bbox.
>  
> But now there is no access to wmts - I see no 'GET' in mapproxy-util output.
> util/httpd is running but no result, no timeout, only waiting.
>  
>  
>  
> I tried the 3 different bounding boxes (mentioned above) and I tried different coverages.
> But there is no result, not a single GET.
> BTW: I have other WMTS/WMS definitions they can access and deliver results.
>  
> I am no Python programmer. Therefore I don't know bbox for WMTS access is calculated.
> Currently I think it should be the bbox I calculate from <TileMatrix> (3).
> Is this correct?  <--- Question 2
>  
> After this I consider the question about the missing GETs.
>  
>  
> Thank you,
> Heinrich Starck
> 
> 
> Diese Mitteilung ist vertraulich und nur fuer den Adressaten bestimmt. Weitergabe oder Vervielfaeltigung durch andere als den Adressaten ist verboten. Wenn Sie die Sendung irrtuemlich erhalten, verstaendigen Sie bitte unverzueglich den Absender.
> This message is confidential. It may not be disclosed to, or used by, anyone other than the addressee. If you receive this message by mistake, please advise the sender.
> _______________________________________________
> MapProxy mailing list
> MapProxy at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/mapproxy





More information about the MapProxy mailing list