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:
EPSG:4326:6
17
18
71
72
However, if i send a request to the server.
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