Timeline for GeoServer on cascading WMTS sets wrong CRS
Current License: CC BY-SA 4.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 21, 2019 at 11:44 | comment | added | Ian Turton | please continue this on the geoserver-user list | |
| Jan 21, 2019 at 11:23 | comment | added | SS_Rebelious | There is no time estimation to close the bug in the ticket. How much time will it take and what price are we talking about? If fixing this bug will be sponsored which GeoServer versions will be fixed? Would it be possible to patch existing installations? | |
| Jan 21, 2019 at 10:53 | comment | added | Ian Turton | It hasn't been fixed so it will continue in all versions since 2.14.x onwards. I believe all the test servers used defined epsg:4326 so it went unnoticed. | |
| Jan 21, 2019 at 10:31 | comment | added | SS_Rebelious | Is there a workaround? Does this bug relate only to WMTS in 2.14.2? In 2.12.5 I have same issue with cascading WMS. Is cascading feature is bugged in every version and for each protocol? BTW out of pure curiosity, is TDD used for GeoServer development? | |
| Jan 21, 2019 at 10:03 | history | answered | Ian Turton | CC BY-SA 4.0 |