Re: [Geoserver-users] Update from Geoserver 2.14 to 2.22 : WFS 1.1.0 result missing Z coordinate
As Ian indicated we added support for XY, XYZ, XYM, XYZM coordinates - the EPSG:3857 srs you have selected is two dimensional for XY data. You can process your data, choose an XYZ srs, or configure the geoserver to consider Z as a measure (which should change the GML output). -- Jody Garnett On Thu, Mar 30, 2023 at 8:56 AM francois roussel wrote: > Hi all, > > I am trying to update from Geoserver 2.14 to 2.22. My Geoserver 2.22 > instance starts on a copy of the 2.14 instance's data. Everything looks > good from the administration console. > > A major difference is present in the WFS responses : This one is from > Geoserver 2.14 > > http://www.opengis.net/gml/srs/epsg.xml#3857"; > srsDimension="3"> > > > 676197.14171868 6332811.49687361 0 676205.71421278 > 6332795.82409933 0 676220.6667465 6332779.85090715 0 676244.61888527 > 6332759.23118246 0 676283.79094172 6332732.20673133 0 676325.2299601 > 6332703.43080496 0 676356.11501381 6332741.40711378 0 676382.92919821 > 6332782.03057298 0 676396.72379804 6332804.57979136 0 676404.37781378 > 6332825.87365151 0 > > > > > And this one is from Geoserver 2.22 > > http://www.opengis.net/gml/srs/epsg.xml#3857"; srsDimension="3"> > > > 676197.14171868 6332811.49687361 676205.71421278 > 6332795.82409933 676220.6667465 6332779.85090715 676244.61888527 > 6332759.23118246 676283.79094172 6332732.20673133 676325.2299601 > 6332703.43080496 676356.11501381 6332741.40711378 676382.92919821 > 6332782.03057298 676396.72379804 6332804.57979136 676404.37781378 > 6332825.87365151 > > > > > As you can see, the Z coordinate is absent from the Geoserver 2.22 > response despite the srsDimension value '3'. As a result, my code can't > deserialize the LineString anymore. > > If I switch my WFS request to WFS=1.0.0 on Geoserver 2.22, the Z > coordinate is present : > > http://www.opengis.net/gml/srs/epsg.xml#3857 > "> > > > http://www.opengis.net/gml"; decimal="." > cs="," ts=" ">676197.14171868,6332811.49687361,0 > 676205.71421278,6332795.82409933,0 676220.6667465,6332779.85090715,0 > 676244.61888527,6332759.23118246,0 676283.79094172,6332732.20673133,0 > 676325.2299601,6332703.43080496,0 676356.11501381,6332741.40711378,0 > 676382.92919821,6332782.03057298,0 676396.72379804,6332804.57979136,0 > 676404.37781378,6332825.87365151,0 > > > > > I took some hours to search about this issue but didn't find anything. Is > it a configuration issue ? How could the srsDimension be correct (3) but > the Z value ignored only for WFS 1.1.0 ? > > Best regards. > ___ > Geoserver-users mailing list > > Please make sure you read the following two resources before posting to > this list: > - Earning your support instead of buying it, but Ian Turton: > http://www.ianturton.com/talks/foss4g.html#/ > - The GeoServer user list posting guidelines: > http://geoserver.org/comm/userlist-guidelines.html > > If you want to request a feature or an improvement, also see this: > https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer > > > Geoserver-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/geoserver-users > ___ Geoserver-users mailing list Please make sure you read the following two resources before posting to this list: - Earning your support instead of buying it, but Ian Turton: http://www.ianturton.com/talks/foss4g.html#/ - The GeoServer user list posting guidelines: http://geoserver.org/comm/userlist-guidelines.html If you want to request a feature or an improvement, also see this: https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users
Re: [Geoserver-users] Update from Geoserver 2.14 to 2.22 : WFS 1.1.0 result missing Z coordinate
We have had a number of issues in the past with M and Z coordinates https://osgeo-org.atlassian.net/browse/GEOT-6096 https://osgeo-org.atlassian.net/browse/GEOT-1716 https://osgeo-org.atlassian.net/browse/GEOS-10667 https://osgeo-org.atlassian.net/browse/GEOT-6740 https://osgeo-org.atlassian.net/browse/GEOT-6599 https://osgeo-org.atlassian.net/browse/GEOT-6362 https://osgeo-org.atlassian.net/browse/GEOT-4337 https://osgeo-org.atlassian.net/browse/GEOS-9520 for example. What is your datasource? We need a small sample that demonstrates the issue before anyone can consider looking at it. Ian On Thu, 30 Mar 2023 at 16:57, francois roussel wrote: > Hi all, > > I am trying to update from Geoserver 2.14 to 2.22. My Geoserver 2.22 > instance starts on a copy of the 2.14 instance's data. Everything looks > good from the administration console. > > A major difference is present in the WFS responses : This one is from > Geoserver 2.14 > > http://www.opengis.net/gml/srs/epsg.xml#3857"; > srsDimension="3"> > > > 676197.14171868 6332811.49687361 0 676205.71421278 > 6332795.82409933 0 676220.6667465 6332779.85090715 0 676244.61888527 > 6332759.23118246 0 676283.79094172 6332732.20673133 0 676325.2299601 > 6332703.43080496 0 676356.11501381 6332741.40711378 0 676382.92919821 > 6332782.03057298 0 676396.72379804 6332804.57979136 0 676404.37781378 > 6332825.87365151 0 > > > > > And this one is from Geoserver 2.22 > > http://www.opengis.net/gml/srs/epsg.xml#3857"; srsDimension="3"> > > > 676197.14171868 6332811.49687361 676205.71421278 > 6332795.82409933 676220.6667465 6332779.85090715 676244.61888527 > 6332759.23118246 676283.79094172 6332732.20673133 676325.2299601 > 6332703.43080496 676356.11501381 6332741.40711378 676382.92919821 > 6332782.03057298 676396.72379804 6332804.57979136 676404.37781378 > 6332825.87365151 > > > > > As you can see, the Z coordinate is absent from the Geoserver 2.22 > response despite the srsDimension value '3'. As a result, my code can't > deserialize the LineString anymore. > > If I switch my WFS request to WFS=1.0.0 on Geoserver 2.22, the Z > coordinate is present : > > http://www.opengis.net/gml/srs/epsg.xml#3857 > "> > > > http://www.opengis.net/gml"; decimal="." > cs="," ts=" ">676197.14171868,6332811.49687361,0 > 676205.71421278,6332795.82409933,0 676220.6667465,6332779.85090715,0 > 676244.61888527,6332759.23118246,0 676283.79094172,6332732.20673133,0 > 676325.2299601,6332703.43080496,0 676356.11501381,6332741.40711378,0 > 676382.92919821,6332782.03057298,0 676396.72379804,6332804.57979136,0 > 676404.37781378,6332825.87365151,0 > > > > > I took some hours to search about this issue but didn't find anything. Is > it a configuration issue ? How could the srsDimension be correct (3) but > the Z value ignored only for WFS 1.1.0 ? > > Best regards. > ___ > Geoserver-users mailing list > > Please make sure you read the following two resources before posting to > this list: > - Earning your support instead of buying it, but Ian Turton: > http://www.ianturton.com/talks/foss4g.html#/ > - The GeoServer user list posting guidelines: > http://geoserver.org/comm/userlist-guidelines.html > > If you want to request a feature or an improvement, also see this: > https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer > > > Geoserver-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/geoserver-users > -- Ian Turton ___ Geoserver-users mailing list Please make sure you read the following two resources before posting to this list: - Earning your support instead of buying it, but Ian Turton: http://www.ianturton.com/talks/foss4g.html#/ - The GeoServer user list posting guidelines: http://geoserver.org/comm/userlist-guidelines.html If you want to request a feature or an improvement, also see this: https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users
[Geoserver-users] Update from Geoserver 2.14 to 2.22 : WFS 1.1.0 result missing Z coordinate
Hi all, I am trying to update from Geoserver 2.14 to 2.22. My Geoserver 2.22 instance starts on a copy of the 2.14 instance's data. Everything looks good from the administration console. A major difference is present in the WFS responses : This one is from Geoserver 2.14 http://www.opengis.net/gml/srs/epsg.xml#3857"; srsDimension="3"> 676197.14171868 6332811.49687361 0 676205.71421278 6332795.82409933 0 676220.6667465 6332779.85090715 0 676244.61888527 6332759.23118246 0 676283.79094172 6332732.20673133 0 676325.2299601 6332703.43080496 0 676356.11501381 6332741.40711378 0 676382.92919821 6332782.03057298 0 676396.72379804 6332804.57979136 0 676404.37781378 6332825.87365151 0 And this one is from Geoserver 2.22 http://www.opengis.net/gml/srs/epsg.xml#3857"; srsDimension="3"> 676197.14171868 6332811.49687361 676205.71421278 6332795.82409933 676220.6667465 6332779.85090715 676244.61888527 6332759.23118246 676283.79094172 6332732.20673133 676325.2299601 6332703.43080496 676356.11501381 6332741.40711378 676382.92919821 6332782.03057298 676396.72379804 6332804.57979136 676404.37781378 6332825.87365151 As you can see, the Z coordinate is absent from the Geoserver 2.22 response despite the srsDimension value '3'. As a result, my code can't deserialize the LineString anymore. If I switch my WFS request to WFS=1.0.0 on Geoserver 2.22, the Z coordinate is present : http://www.opengis.net/gml/srs/epsg.xml#3857";> http://www.opengis.net/gml"; decimal="." cs="," ts=" ">676197.14171868,6332811.49687361,0 676205.71421278,6332795.82409933,0 676220.6667465,6332779.85090715,0 676244.61888527,6332759.23118246,0 676283.79094172,6332732.20673133,0 676325.2299601,6332703.43080496,0 676356.11501381,6332741.40711378,0 676382.92919821,6332782.03057298,0 676396.72379804,6332804.57979136,0 676404.37781378,6332825.87365151,0 I took some hours to search about this issue but didn't find anything. Is it a configuration issue ? How could the srsDimension be correct (3) but the Z value ignored only for WFS 1.1.0 ? Best regards. ___ Geoserver-users mailing list Please make sure you read the following two resources before posting to this list: - Earning your support instead of buying it, but Ian Turton: http://www.ianturton.com/talks/foss4g.html#/ - The GeoServer user list posting guidelines: http://geoserver.org/comm/userlist-guidelines.html If you want to request a feature or an improvement, also see this: https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users
