Open issues

Uploading Geojson format to geonode 2.10.1, not all records in the features gets uploaded
GEOS-9325
Getting error in ysld and css style in GeoServer
GEOS-9310
Unauthenticated Vulnerability
GEOS-9201
Bypass for GEOS-7848
GEOS-8552
Error when trying to publish an Image Mosaic JDBC layer
GEOS-8278
Wrong background values with ImageMosaicJDBC and 32bit Real images
GEOS-7582
Rendering process failed java.io.IOException No more data to read from socket
GEOS-7021
LDAP authentication fails with "invalid DN"
GEOS-6894
Unable to delete layer from geoserver folder
GEOS-9349
Fresh install - GeoServer will not start
GEOS-9347
WCS 2 - CRS Extension not implemented correctly
GEOS-9328
Importer DataStore connection error when running multiple tasks
GEOS-9323
The develop manual "Implementing a RESTful Service" of GeoServer 2.14.x is incorrect
GEOS-9306
json response is not consistent for get layers REST call
GEOS-9300
GeoFence and External Web Map Server
GEOS-9294
external legend graphics problems using GeoServer 2.14
GEOS-9177
contents.ftl template parsing a hash causes Service Exception
GEOS-9089
[Backup & Restore] Improve the module Documentation with the latest fixes/improvements
GEOS-9078
TileMatrixSets' supported CRS are ignored when consuming WMTS service
GEOS-9042
File upload via /rest/resource interface results in unusable files.
GEOS-8998
[Label Placement] Baseline is displaced when the label has line breaks and descenders
GEOS-8975
Creating ImageMosaic with Geoserver REST API produces inappropriate coverage parameters types
GEOS-8745
A bunch of Accentuated words are broken since 2.13.0 (french é => � )
GEOS-8731
gwc style and layer workspace global services disabled
GEOS-8704
Problem with GeoFence roles checking
GEOS-8686
Error during GeoServer bootstrapping (InsufficientAuthenticationException)
GEOS-8654
Enabling CSW in workspace does not work
GEOS-8625
http error: 404 when install jai_imageio
GEOS-8594
NetCDF Auxiliary Store reports error file doesn't exist when file is present
GEOS-8584
REST API - Add an option to get all LayerGroups, with and without a workspace specified
GEOS-8518
NPE on cascaded WMS during GetMap (ResourcePool.getWMSLayer)
GEOS-8268
Unable to create layers using MBTiles
GEOS-8241
CLONE - GeoWebCache settings won't be persisted on Windows
GEOS-7783
After update grib file I have carusel of dimension name (depth_below_sea, depth_below_sea1, depth_below_sea2). No way to configure dimension.
GEOS-7714
Signed 8bit
GEOS-7590
Porter-Duff composite is wrong when tiled option is true
GEOS-7569
ImageMosaic GetFeatureInfo returning wrong value
GEOS-7568
WFS version 2.0.0 requests with Filter String Property Literals starting with leading zero returns not working
GEOS-7540
Windows service wrapper appears to have problematic license
GEOS-7488
Java process segfault in LCMS library
GEOS-7458
Digest authentication is broken
GEOS-7404
java.lang.ClassCastException: java.util.ArrayList cannot be cast to org.opengis.feature.type.AttributeDescriptor
GEOS-7244
bad or not json output via rest call to layergroup
GEOS-7232
ArcSDE Direct Connect not working
GEOS-7179
Inconsistent value for "Infinite" and "-Infinity" in WFS-GML : getting INF anf -Infinity
GEOS-4909
WCS Memory Leak
GEOS-3219
Oracle SQL View with NULL SRID breaks Bounds calculations on BasicResourceConfig
GEOS-9399
Cached layers page may take minutes to show up (when backing stores are not responsive)
GEOS-9397
Fetch remote styles and image formats on demand in Cascaded WMS Settings
GEOS-9396
Cascaded WMS Documentation update
GEOS-9393
issue 19 of 909

TileMatrixSets' supported CRS are ignored when consuming WMTS service

Description

When creating a WMTS store and publishing layers from that store, Geoserver seems to ignore the supported CRS's set in the TileMatrixSets and always thinks the native SRS is WGS84 (4326). I have tried the following WMTS services:

http://geodata.nationaalgeoregister.nl/luchtfoto/infrarood/wmts?request=GetCapabilities&service=WMTS
http://wmts.kartetirol.at/wmts
https://api.lantmateriet.se/open/topowebb-ccby/v1/wmts/token/8d61b10d-e93b-3c04-b4ae-4f4bdd1afe1b/?request=getcapabilities&service=wmts

In my case I need to use the last of the three services (api.lantmateriet.se) and publish a SWEREF99 (3006) layer. The service provides one TileMatrixSet supporting WGS84/Pseudo-mercator (3857) and one supporting SWEREF99 (3006). Trying to reproject to or force the use of the declared SWEREF99 creates a broken map with overlapping tiles (this somehow works for 3857 though).

A couple of things worth noting:

  • When I press the publish/publish again links for the store, the geoserver log says “Skipping WGS 84 / Pseudo-Mercator definition, it was not recognized by the referencing subsystem” and “Skipping SWEREF99 TM definition, it was not recognized by the referencing subsystem”. That seems relevant but I don’t know what it means. Other systems can consume the service as described below.

  • Opening the WMTS connection from QGIS 3.4.2 results in a tree structure with the two layers at the top and under them the two tile matrices (named 3006 and 3857 after the supported SRS’es). When adding one of the layers’ 3006 TileMatrix, the map displays perfectly. In Geoserver, shouldn't you get to choose which TileMatrixSet to use like in QGIS?

The tokens in the URL's will get invalidated after a while but the data is open so anyone can create an account at https://opendata.lantmateriet.se and generate their own.

Environment

None

Status

Assignee

Ian Turton

Reporter

Henrik Pierrou

Triage

None

Fix versions

None

Affects versions

2.14.1

Components

Priority

High
Configure