Hello guys,
we implemented the WMTS protocol on client side. We were using currently
geoserver 2.1.x
but now we want to use the latest geoserver.
However, we found out, that there is some difference in the
getCapabilities. If I execute it
on 2.1.x it returns things like that:
<TileMatrix>EPSG:4326:6</TileMatrix>
<MinTileRow>17</MinTileRow>
<MaxTileRow>18</MaxTileRow>
<MinTileCol>71</MinTileCol>
<MaxTileCol>72</MaxTileCol>
However, if i send a request to the server.
http://127.0.0.1:8080/geoserver/gwc/service/wmts?TILECOL=72&LAYER=maced&FORMAT=image/jpeg&TILEMATRIX=EPSG:4326:6&TILEMATRIXSET=EPSG:4326&STYLE=_null&REQUEST=GetTile&TILEROW=18&VERSION=1.0.0
I get a row number error.
Row 18 is out of range, min: 16 max:17
If i decrease the row number with 1, it works perfectly. It seems that i
buggy (or done by specification, i don't know) in geoserver 2.1.x.
Interestingly, this bug seems to be fixed in latest (2.3.x) geoserver. Is
this correct? Is there some backward compatibility mode to support the old
numbering also, or should i have to add a parameter in our application to
support both the old numbering and the new one?
Thanks,
Zsolti
------------------------------------------------------------------------------
Precog is a next-generation analytics platform capable of advanced
analytics on semi-structured data. The platform includes APIs for building
apps and a phenomenal toolset for data science. Developers can use
our toolset for easy data analysis & visualization. Get a free account!
http://www2.precog.com/precogplatform/slashdotnewsletter
_______________________________________________
Geoserver-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-users
