You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It seems there is some history regarding the axis ordering with 4326 and looking at other OGC GetCapabilities Request and WMTSCapabilities.xml online; TileSets of EPSG:4326 specify [lat lon] for the top left corner; but for CRS84 it is [lon lat].
Setting that value to true fixes my issue. Should yCoordinateFirst change based on the detected CRS?
Could it be related to the fact that when publishing a TPK created in ArcGIS Pro in EPSG:2180 (Poland), the map display of WMTS is offset somewhere in the Indian Ocean?
Testing 1.23.RC1 for WMTS of an ArcGIS Tile Cache, first release since 1.10.5 that works (#1012).
The cached tiles are EPSG:4326. Here is an excerpt of the conf.xml
The ordering is expected to be yCoordinateFirst when being loaded by ArcGIS Javascript API. This value is hardcoded in GridSetBuilder to false.
https://github.com/GeoWebCache/geowebcache/blob/1.23-RC1/geowebcache/arcgiscache/src/main/java/org/geowebcache/arcgis/layer/GridSetBuilder.java#L61
It seems there is some history regarding the axis ordering with 4326 and looking at other OGC GetCapabilities Request and WMTSCapabilities.xml online; TileSets of EPSG:4326 specify [lat lon] for the top left corner; but for CRS84 it is [lon lat].
Setting that value to true fixes my issue. Should yCoordinateFirst change based on the detected CRS?
Some references:
The text was updated successfully, but these errors were encountered: