id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc
17118	Sort out axis=neu for EPSG:4326	Don-vip	team	"We define EPSG:4326 with `axis=neu` since r8584 to get WMTS working:
{{{
# WGS 84
<4326> +proj=lonlat +datum=WGS84 +axis=neu +bounds=-180,-90,180,90  <>
}}}

Yet we have currently the `Saxony latest aerial imagery` WMTS in [[Maps/Germany]] which [https://geodienste.sachsen.de/wmts_geosn_dop-rgb/guest?REQUEST=GetCapabilities&SERVICE=WMTS defines] its EPSG:4326 tile matrix as follows:

{{{
#!xml
<TileMatrixSet>
  <ows:Identifier>grid_4326</ows:Identifier>
  <ows:SupportedCRS>EPSG:4326</ows:SupportedCRS>
  <TileMatrix>
    <ows:Identifier>00</ows:Identifier>
    <ScaleDenominator>17471320.7509</ScaleDenominator>
    <TopLeftCorner>11.7 51.7</TopLeftCorner>
}}}

We cannot use this matrix with JOSM as it assumes the coordinates being inverted, resulting in negative tile coordinates. This makes the [/jenkins/job/JOSM-Integration/lastCompletedBuild/jdk=JDK8/testReport/org.openstreetmap.josm.gui.preferences.imagery/ImageryPreferenceTestIT/testValidityOfAvailableImageryEntries/ imagery integration test] fail (see #16073).

Who's wrong? Saxony's WMTS server or us?"	defect	reopened	normal		External imagery source			projection wgs84 axis wmts	wiktorn