Jukka, you're right the transaction should come with the urn style crs identifier. The behavior is not a bug, is by design. As he's using WFS 1.1, the urn style crs identifier should be used to respect the ESPG database axis order. Using the "EPSG:xxx" crs style identifier to mean "force X/Y lon/lat axis order"
Cheers, Gabriel On Fri, Mar 30, 2012 at 1:05 AM, Rahkonen Jukka <[email protected]> wrote: > Hi, > > You are right, things should go in a similar way, right or wrong, with both > inserts and updates. This feels like a bug. > > Could you have another try with this urn-style srsName > urn:ogc:def:crs:EPSG::3007 > > And then it would not harm to add srsName also to the geometries in > inserts/updates. Then there is less play with the defaults. We seem to get > this kind of inputs for our system > > <gml:Point srsName="urn:ogc:def:crs:EPSG::3067"> > <gml:pos srsDimension="2">385338.63323124044 6680121.5237366</gml:pos> > </gml:Point> > > -Jukka Rahkonen- > > Sjoerd Brandsma wrote: >> >> Hi Jukka, >> >> Thanks for your answer. I'm not really an coordinate system export but >> when it's an easting, northing issue things should also fail when >> doing an insert? >> >> What basically happens (when using EPSG:3007 and Geoserver 2.1.1): >> >> Insert two values (let's call them A and B) with WFS-T insert. With >> Postgresql this is read back as A,B >> Update two values (let's call them A' and B') with WFS-T update. With >> Postgresql this is read back as B', A' >> >> I cannot think of any reason why I should swap A and B when doing an >> update and not doing this with an insert. >> >> >> Thanks for your help. >> >> Best regards, >> Sjoerd Brandsma >> CycloMedia >> >> On Fri, Mar 30, 2012 at 6:26 AM, Rahkonen Jukka >> <[email protected]> wrote: >> > Hi, >> > Are these EPSG data correct? >> > >> > >> http://www.epsg-registry.org/report.htm?type=selection&entity= > urn:ogc:def:crs:EPSG::3007&reportDetail=short&style=urn:uuid:report-> > style:default-with-urn&style_name=OGP%20Default%20With%20Urn&title=swe >> > >> > It tells that the first coordinate is northing, second >> easting. PostGIS lists coordinates always as easting, >> northing. If EPSG info is t´right, you should flip the >> coordinates in your update GML into >> > <gml:pos> 6397415.081100176 145944.27274535838</gml:pos> >> > >> > -Jukka Rahkonen- >> > ________________________________________ >> > Sjoerd Brandsma wrote: >> > >> >> Hi, >> > >> >> I'm experiencing some weird problems with a WFS-T update >> with EPSG:3007. >> > >> >> When inserting a point with the following transaction: >> > >> > <wfs:Transaction service="WFS" version="1.1.0" >> > xmlns:wfs="http://www.opengis.net/wfs";> >> > <wfs:Insert inputFormat="text/xml; subtype=gml/3.1.1" >> srsName="EPSG:3007"> >> > <SE:inventory_project_e45got_verkeer_2012 >> > xmlns:SE="http://www.cyclomedia.se";> >> > <SE:the_geom xlink:type="simple" >> > xmlns:xlink="http://www.w3.org/1999/xlink";> >> > <gml:Point xmlns:gml="http://www.opengis.net/gml";> >> > <gml:pos>145944.27274535838 6397415.081100176</gml:pos> >> > </gml:Point> >> > </SE:the_geom> >> > </SE:inventory_project_e45got_verkeer_2012> >> > </wfs:Insert> >> > </wfs:Transaction> >> > >> > The following PostgreSql is executed to get the point information: >> > SELECT st_asewkt(the_geom) FROM >> inventory_project_e45got_verkeer_2012 >> > This gives the following (correct) result: >> > "SRID=3007;POINT(145944.272745358 6397415.08110018)" >> > >> > Then an update transaction is performed: >> > >> > <wfs:Transaction service="WFS" version="1.1.0" >> > xmlns:wfs="http://www.opengis.net/wfs";> >> > <wfs:Update typeName="SE:inventory_project_e45got_verkeer_2012" >> > inputFormat="text/xml; subtype=gml/3.1.1" srsName="EPSG:3007" >> > xmlns:SE="http://www.cyclomedia.se";> >> > <wfs:Property> >> > <wfs:Name>SE:the_geom</wfs:Name> >> > <wfs:Value> >> > <gml:Point xmlns:gml="http://www.opengis.net/gml";> >> > <gml:pos>145944.30681447688 6397415.045897427</gml:pos> >> > </gml:Point> >> > </wfs:Value> >> > </wfs:Property> >> > <ogc:Filter xmlns:ogc="http://www.opengis.net/ogc";> >> > <ogc:GmlObjectId >> > gml:id="inventory_project_e45got_verkeer_2012.696" >> > xmlns:gml="http://www.opengis.net/gml"/> >> > </ogc:Filter> >> > </wfs:Update> >> > >> > With the SQL query the point now has X and Y swapped >> > "SRID=3007;POINT(6397415.04589743 145944.306814477)" >> > >> > >> > Any idea what can be the problem here? >> > >> > Thanks, >> > >> > Sjoerd Brandsma >> > CycloMedia >> > >> > >> -------------------------------------------------------------- >> ---------------- >> > This SF email is sponsosred by: >> > Try Windows Azure free for 90 days Click Here >> > http://p.sf.net/sfu/sfd2d-msazure >> > _______________________________________________ >> > Geoserver-users mailing list >> > [email protected] >> > https://lists.sourceforge.net/lists/listinfo/geoserver-users >> > ------------------------------------------------------------------------------ > This SF email is sponsosred by: > Try Windows Azure free for 90 days Click Here > http://p.sf.net/sfu/sfd2d-msazure > _______________________________________________ > Geoserver-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/geoserver-users -- Gabriel Roldan OpenGeo - http://opengeo.org Expert service straight from the developers. ------------------------------------------------------------------------------ This SF email is sponsosred by: Try Windows Azure free for 90 days Click Here http://p.sf.net/sfu/sfd2d-msazure _______________________________________________ Geoserver-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-users
