Since the newer versions of geoserver does handle the axis order on another way then the older versions, it may come to problems when using wfs-t with some crs like EPSG:4326 or EPSG:31466. Therefor we need some workaround, which will be defined in the digitizing functions. First javascripts/mod_digitize_tab.php will need an optional variable which switch the axis order of the geojson objects before pushing them to wfs-t. On the other hand we may need an option to switch the axis order from the gazetteer result list - when the geometries are pushed to the digitize module.
The central geometry.js class has to be adopted.
Since the newer versions of geoserver does handle the axis order on another way then the older versions, it may come to problems when using wfs-t with some crs like EPSG:4326 or EPSG:31466. Therefor we need some workaround, which will be defined in the digitizing functions. First javascripts/mod_digitize_tab.php will need an optional variable which switch the axis order of the geojson objects before pushing them to wfs-t. On the other hand we may need an option to switch the axis order from the gazetteer result list - when the geometries are pushed to the digitize module.
The central geometry.js class has to be adopted.