[MapProxy] Problem with EPSG:31254 (MGI-Austira_West) (north, west coordinates)

Thorsten Hildebrand (WhereGroup) thorsten.hildebrand at wheregroup.com
Wed Mar 12 22:24:58 PDT 2025


Hi Andy,

have a look at the settings for axis_order_ne and axis_order_en at: 
https://mapproxy.github.io/mapproxy/latest/configuration.html#id13

Try to explicitly specify the WMS version with your requests.

> If you follow the definition of 31254
> (coordinate system: Cartesian 2D CS. Axes: northing, easting (X,Y). 
> Orientations: north, east.)
> X should be north and Y should be east.

...
The axis ordering defines in which order coordinates are given, i.e. 
lon/lat or lat/lon. The ordering is dependent to the SRS. Most clients 
and servers did not respect the ordering and everyone used lon/lat 
ordering. With the WMS 1.3.0 specification the OGC emphasized that the 
axis ordering of the SRS should be used.

Here you can define the axis ordering of your SRS. This might be 
required for proper WMS 1.3.0 support if you use any SRS that is not in 
the default configuration.

By default MapProxy assumes lat/long (north/east) order for all 
geographic and x/y (east/north) order for all projected SRS.
...

> In our production environment we still use an old Centos-Box (Python 3.6 
> and mapproxy 1.12) and there everything works fine.

Also note the change in this topic in MapProxy version 1.13.0
...
Changed in version 1.13.0: MapProxy can now determine the correct axis 
order for all coordinate systems when using pyproj>=2. The 
axis_order_ne/axis_order_en are ignored in this case.
...

Greetings from Berlin,
Thorsten

--
Thorsten Hildebrand
WhereGroup GmbH
Bundesallee 23
10717 Berlin
Germany

Tel: +49 (0)30 / 513 02 78 - 75
Fax: +49 (0)30 / 513 02 78 - 11

thorsten.hildebrand at wheregroup.com
www.wheregroup.com

Geschäftsführer:
Olaf Knopp, Peter Stamm
Amtsgericht Bonn, HRB 9885




More information about the MapProxy mailing list