after upgrading GeoServer from 2.24.0 to 2.24.1 one of my users was unable to process data from the WFS service in the software FME. The problem comes from the fact that the feature type returned in the GetFeature request doesn’t match the feature type declared in the DescribeFeatureType request when accessing the service using WFS 1.1.0. In this case FME doesn’t detect the geometries.
This can be reproduced using the ‘ne:countries’ layer in a new GeoServer installation. This is what my tests showed:
Please remember that GeoServer is maintained by volunteers - if your users have a problem then they are (presumably) paying you to take care of it. If you are not up to fixing the problem yourself please contact one of the commercial support teams that will look into it for you.
I made a test with Geoserver 2.25.0 and I can confirm that there is a mismatch between DescribeFeatureType and GetFeature for ne:countries with WFS 1.1.0.
I tried to test also topp:states but it seems that there is something else broken with that. GetFeature with WFS 1.1.0 and WFS 2.0 returns this error:
<ows:Exception exceptionCode=“NoApplicableCode”>
ows:ExceptionTextWe have had issues trying to flip axis of GEOGCS[“GCS_WGS_1984”, DATUM[“WGS_1984”, SPHEROID[“WGS_1984”, 6378137.0, 298.257223563]], PRIMEM[“Greenwich”, 0.0], UNIT[“degree”, 0.017453292519943295], AXIS[“Longitude”, EAST], AXIS[“Latitude”, NORTH]] No authority was defined for code “GCS_WGS_1984”. Did you forget “AUTHORITY:NUMBER”?</ows:ExceptionText>
I was testing with a new Geoserver binzip installation on Windows, JVM Eclipse Adoptium: 11.0.22.
-Jukka Rahkonen-
···
Lähettäjä: Ian Turton <ijturton@anonymised.com4…> Lähetetty: maanantai 22. huhtikuuta 2024 19.00 Vastaanottaja: Calliess Daniel Ing. Daniel.Calliess@anonymised.com Kopio: geoserver-users geoserver-users@lists.sourceforge.net Aihe: Re: [Geoserver-users] Geometry type mismatch
after upgrading GeoServer from 2.24.0 to 2.24.1 one of my users
Please look into this and correct the error.
Please remember that GeoServer is maintained by volunteers - if your users have a problem then they are (presumably) paying you to take care of it. If you are not up to fixing the problem yourself please contact one of the commercial support teams that will look into it for you.
Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si precisa che ogni circostanza inerente alla presente email (il suo contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra operazione è illecita. Le sarei comunque grato se potesse darmene notizia.
This email is intended only for the person or entity to which it is addressed and may contain information that is privileged, confidential or otherwise protected from disclosure. We remind that - as provided by European Regulation 2016/679 “GDPR” - copying, dissemination or use of this e-mail or the information herein by anyone other than the intended recipient is prohibited. If you have received this email by mistake, please notify us immediately by telephone or e-mail
Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si precisa che ogni circostanza inerente alla presente email (il suo contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra operazione è illecita. Le sarei comunque grato se potesse darmene notizia.
This email is intended only for the person or entity to which it is addressed and may contain information that is privileged, confidential or otherwise protected from disclosure. We remind that - as provided by European Regulation 2016/679 “GDPR” - copying, dissemination or use of this e-mail or the information herein by anyone other than the intended recipient is prohibited. If you have received this email by mistake, please notify us immediately by telephone or e-mail
From: Andrea Aime <andrea.aime@…10949…> Sent: Dienstag, 23. April 2024 10:31 To: Calliess Daniel Ing. <Daniel.Calliess@…8499…> Cc: geoserver-users geoserver-users@lists.sourceforge.net Subject: [EXTERN!]: Re: [Geoserver-users] Geometry type mismatch
Hi Daniel,
the issue is not recorded yet in Jira, I invite you to file a report there:
Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si precisa che ogni circostanza inerente alla presente email (il suo contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra operazione è illecita. Le sarei comunque grato se potesse darmene notizia.
This email is intended only for the person or entity to which it is addressed and may contain information that is privileged, confidential or otherwise protected from disclosure. We remind that - as provided by European Regulation 2016/679 “GDPR” - copying, dissemination or use of this e-mail or the information herein by anyone other than the intended recipient is prohibited. If you have received this email by mistake, please notify us immediately by telephone or e-mail
after upgrading GeoServer from 2.24.0 to 2.24.1 one of my users was unable to process data from the WFS service in the software FME. The problem comes from the fact that the feature type returned in the GetFeature request doesn’t match the feature type declared in the DescribeFeatureType request when accessing the service using WFS 1.1.0. In this case FME doesn’t detect the geometries.
This can be reproduced using the ‘ne:countries’ layer in a new GeoServer installation. This is what my tests showed:
GeoServer 2.24.0
WFS 1.0.0
GetFeature = MultiPolygon
DescribeFeatureType = MultiPolygonPropertyType
WFS 1.1.0
GetFeature = MultiSurface
DescribeFeatureType = MultiSurfacePropertyType
WFS 2.0.0
GetFeature = MultiSurface
DescribeFeatureType = MultiSurfacePropertyType
GeoServer 2.24.1
WFS 1.0.0
GetFeature = MultiPolygon
DescribeFeatureType = MultiPolygonPropertyType
WFS 1.1.0
GetFeature = MultiSurface
DescribeFeatureType = MultiPolygonPropertyType
WFS 2.0.0
GetFeature = MultiSurface
DescribeFeatureType = MultiSurfacePropertyType
Please look into this and correct the error.
Thank you and best regards
Daniel
Geoserver-users mailing list
Please make sure you read the following two resources before posting to this list:
last year I created an issue regarding this problem and according to the information there, a fix has been merged. I just tested this in GeoServer 2.27, but the problem persists. Does anyone have an idea why this fix didn’t make it into the release version of GeoServer?