search

geosolutions-it / ogc-vtp-2018

Report for the OGC Vector Tiles Pilot 2018
https://waffle.io/geosolutions-it/ogc-vtp-2018
0 stars 0 forks source link

Follow up on Jerome's WMTS feedback #12

Closed aaime closed 5 years ago

aaime commented 5 years ago

See list, some complaints about grid description, CRS being used, mime type being used.

aaime commented 5 years ago

In particular (mail quotes and comments):

am trying to make sense of some of the TileMatrixSets @ http://maps.geo-solutions.it/geoserver/vtp/gwc/service/wmts?request=GetCapabilities

<TileMatrixSet>
   <ows:Identifier>EPSG:4326_512</ows:Identifier>
   <ows:SupportedCRS>urn:ogc:def:crs:EPSG::4326</ows:SupportedCRS>
   <TileMatrix><ows:Identifier>EPSG:4326:0</ows:Identifier>
   <ScaleDenominator>2.795411320143589E8</ScaleDenominator>
   <TopLeftCorner>-180.0 270.0</TopLeftCorner>
   ...
<TileMatrixSet>
   <ows:Identifier>EPSG:4326</ows:Identifier>
   <ows:SupportedCRS>urn:ogc:def:crs:EPSG::4326</ows:SupportedCRS>
   <TileMatrix><ows:Identifier>EPSG:4326:0</ows:Identifier>
   <ScaleDenominator>2.795411320143589E8</ScaleDenominator>
   <TopLeftCorner>90.0 -180.0</TopLeftCorner>

It seems that these two (EPSG:4326 vs. EPSG:4326_512) define the TopLeftCorner in a flipped way? Could it be that the 512 version is wrong? Both specify the same supported CRS, and we normally interpret the top left corner to be lat, lon when that is either 'EPSG:4326' or 'urn:ogc:def:crs:EPSG::4326'.

The above must be verified, might be bug or configuration...

Also, would it be possible for GeoServer to use the standardized MIME type to describe the Mapbox vector tiles format? ( application/vnd.mapbox-vector-tile )

This can be solved by changing the GeoServer vector tiles module, but we might want to keep the old format available for backwards compatibility (something to be discussed on the devel list I believe).

<TileMatrixSet>   
  <ows:Identifier>EPSG:900913</ows:Identifier>   
  <ows:SupportedCRS>urn:ogc:def:crs:EPSG::900913</ows:SupportedCRS>

I just realized that 900913 was GoogleMapsCompatible aka WebMercator. It would be nice also if the was specified as it does match the GoogleMapsCompatible WKSS. Most of the other tiling schemes on your WMTS also are all WKSS and could have such an identifier.

This can be addressed as configuration, but we might also raise the issue on the GWC list and have GWC use the well known scale sets from the WMTS specification by default instead of these old ones.

fernandor777 commented 5 years ago

PR sent and merged

fernandor777 commented 5 years ago

2.14 & 2.13 backports needed.

simboss commented 5 years ago

@fernandor777 shouldn't this one be in progress?

simboss commented 5 years ago

@aaime should we really backport to 2.13 and 2.14?

aaime commented 5 years ago

It is an actual bug, anyone setting up a custom gridset in a geographic CRS has axis flipped in the caps document

simboss commented 5 years ago

cool

fernandor777 commented 5 years ago

Backports PRs sent