Open offtherailz opened 1 year ago
Pointing out an obvious bit: trying to use a global layer, like the rain one, with a projection that is meant for local usage (UTM) makes little sense to start with. Most of the layer data is outside of the area where the projection was meant to be used, and in fact, large part of it lays in areas where the math of the projection stops making sense.
There is a small clarification. The layers we publish were originally made and published in the local projection 4026, WMS is published in Mapstore2 correctly, there are problems only with the display of WMTS on Mapstore2 maps in the 4026 projection.
You can use these data to test adding: WMTS https://geodata.gov.md/geoserver/gwc/service/wmts, and WMS http://geodata.gov.md/geoserver/gwc/service/wms
Description
See
How to reproduce
Expected Result WMTS layer is visible on map
Current Result
Browser info
(use this site: https://www.whatsmybrowser.org/ for non expert users) | Browser Affected | Version | |---|---| |Internet Explorer| | |Edge| | |Chrome| | |Firefox| | |Safari| |Other useful information
Sample map connected to local GeoServer configured as the bug suggested. map.zip
localConfig.json to use localConfig.zip
WMTS configugation