You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm currently trying to implement displaying single image WMS layers, and some GIS servers seem to have the X and Y axis swapped. This results in the WMS layer not displayed or displayed at the wrong location. I think the issue can be fixed with a modified bounding box where X and Y coordinates are swapped. One example WMS service: https://geodatenonline.bayern.de/geodatenonline/seiten/wms_fzw
I know that the official WMS specification says that bbox=minX,minY,maxX,maxY, and the WmsMapService class does this correctly. But would there be a possibility to also support those WMS services with swapped axes?
On a side note, in OpenLayers on the JavaScript side, I can support those WMS servers by creating a Projection from EPSG:4326, but with a different axisOrientation ("neu" instead of "enu").
The text was updated successfully, but these errors were encountered:
Sorry for the late response. I understand your point, but currently i have no time to work on the project. At the moment the only thing i could is to review a pull request. 😏
I'm currently trying to implement displaying single image WMS layers, and some GIS servers seem to have the X and Y axis swapped. This results in the WMS layer not displayed or displayed at the wrong location. I think the issue can be fixed with a modified bounding box where X and Y coordinates are swapped. One example WMS service: https://geodatenonline.bayern.de/geodatenonline/seiten/wms_fzw
I know that the official WMS specification says that bbox=minX,minY,maxX,maxY, and the
WmsMapService
class does this correctly. But would there be a possibility to also support those WMS services with swapped axes?On a side note, in OpenLayers on the JavaScript side, I can support those WMS servers by creating a Projection from EPSG:4326, but with a different axisOrientation ("neu" instead of "enu").
The text was updated successfully, but these errors were encountered: