I have an OL app that is using WFS-T to perform some changes on the PostGIS DB served through Geoserver. I am using Geoserver 2.8.0 (but have tried also Geoserver 2.7.2 with the same result) and EPSG:4326.The problem occurs when the WFS-T transaction data is received by Geoserver from OL, for example this is the Transaction part from the Firebug:...
geometry**1.2999916076660156 51.13655090332031**...
The coordinates are perfectly fine here and if I do ST_MakePoint query in PG, I get the correct location on the map.
However, even though Geoserver's log says that it has received the right information update[0]: property[0]: name = geometry value = POINT (1.2999916076660156 51.13655090332031)property[0]: name = key...
I see in the PGSQL log the following query being executed:
UPDATE "public"."mytable" SET "geometry" = ST_GeomFromText('POINT (51.13655090332031 1.2999916076660156)'.....
The point created is of course created on wrong location.
Since the sequence of coordinates is just swapped, I assume that this is a Geoserver's bug or perhaps I am doing something totally wrong?
Thanks for the ideas and suggestions,Matej
أكثر...
geometry**1.2999916076660156 51.13655090332031**...
The coordinates are perfectly fine here and if I do ST_MakePoint query in PG, I get the correct location on the map.
However, even though Geoserver's log says that it has received the right information update[0]: property[0]: name = geometry value = POINT (1.2999916076660156 51.13655090332031)property[0]: name = key...
I see in the PGSQL log the following query being executed:
UPDATE "public"."mytable" SET "geometry" = ST_GeomFromText('POINT (51.13655090332031 1.2999916076660156)'.....
The point created is of course created on wrong location.
Since the sequence of coordinates is just swapped, I assume that this is a Geoserver's bug or perhaps I am doing something totally wrong?
Thanks for the ideas and suggestions,Matej
أكثر...