-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
WFS-NG Check #2492
WFS-NG Check #2492
Conversation
Making some notes:
Testing against GeoServer 2.15.2:
Layer preview shows inconsistent results:
Examples:
Used Strict CITE compliance for the following tests. Changing srsName as part of request provides some control: WFS 1.1.0 GetFeature GML2, GML3, GML32WFS 2.0
|
ogr output shows WGS84 EPSG:4326:
And showing some content shows X/Y order:
|
Moving this discussion over to geoserver/geoserver#3674 |
So is there anything left to do here? |
@jodygarnett if there is no more activity here I'd suggest to close it, it's been around for a while with no sign of resolution? |
Marking as ready for review, will look at travis-ci failure. As many of the online tests were written for the old implementation they do not all pass; by merging this in it corrects one serious flaw; and allows some tests to be turned on using a geoserver.properties file. |
Signed-off-by: Jody Garnett <jody.garnett@gmail.com>
WFS 2.0 returns a different set up expected features Signed-off-by: Jody Garnett <jody.garnett@gmail.com>
Signed-off-by: Jody Garnett <jody.garnett@gmail.com>
Signed-off-by: Jody Garnett <jody.garnett@gmail.com>
9c767f3
to
e8b28aa
Compare
@aaime thanks for the encouragement, this is ready for your review as an improvement. I can now meet my requirement, and have made it possible to run and pass a few more tests along the way. |
@@ -33,7 +33,7 @@ | |||
public class GeoServerOnlineTest extends AbstractWfsDataStoreOnlineTest { | |||
|
|||
public static final String SERVER_URL = | |||
"http://localhost:9090/geoserver/wfs?service=WFS&request=GetCapabilities&version=2.0.0"; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is the test run on a normal maven build (hopefully not)? There are around a few annoying tests that just fail if there is a GeoServer running locally that does not have the layers they expect.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Checked, no worries, they are not run at all
@@ -33,7 +33,7 @@ | |||
public class GeoServerOnlineTest extends AbstractWfsDataStoreOnlineTest { | |||
|
|||
public static final String SERVER_URL = | |||
"http://localhost:9090/geoserver/wfs?service=WFS&request=GetCapabilities&version=2.0.0"; | |||
"http://localhost:8080/geoserver/wfs?service=WFS&request=GetCapabilities&version=2.0.0"; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We should move this to a test fixture then
I would like to backport this, but I understand a geoserver test case needs to be modified at the same time |
If you need it, @jodygarnett, this is the commit I made for that GeoServer test fix |
Looking at an axis order issue encountered by GeoNetwork when updating to GeoTools 21.x:
Reference: