Hi, Just ran into an issue with GeoServer's WFS service serving WFS 2.0.0 as GML 3.2 from data stored as parquet files in a GeoMesa Filesystem (S3) data store. More precisely I'm trying to visualize those data in QGIS using a WFS layer. With this setup QGIS is unable to render these data. It complains about an "unbound prefix in line 1, column 726" in the WFS GetFeature response. Having a deeper look into the response from GeoServer reveals that the XML namespace of my feature's (i.e. ModemState) elements is null where it should have been "vehicle-events":
<?xml version="1.0" encoding="UTF-8"?> <wfs:FeatureCollection xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:wfs="http://www.opengis.net/wfs/2.0" xmlns:gml="http://www.opengis.net/gml/3.2" xmlns:vehicle-events="urn:athena:vcc:crowd:vehicle-events" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" next="https://develop.vcc.otonomousmobility.com/atvcrwd-geoserver/vehicle-events/wfs?REQUEST=GetFeature&BBOX=48.67796064700979%2C8.97443411395199%2C48.67995793698221%2C8.980798400236115%2Curn%3Aogc%3Adef%3Acrs%3AEPSG%3A%3A4326&SRSNAME=urn%3Aogc%3Adef%3Acrs%3AEPSG%3A%3A4326&VERSION=2.0.0&TYPENAMES=vehicle-events%3AModemState&SERVICE=WFS&COUNT=10&STARTINDEX=10" numberMatched="3054" numberReturned="10" timeStamp="2019-02-27T14:40:11.234Z" xsi:schemaLocation="http://www.opengis.net/wfs/2.0 https://develop.vcc.otonomousmobility.com/atvcrwd-geoserver/schemas/wfs/2.0/wfs.xsd http://www.opengis.net/gml/3.2 https://develop.vcc.otonomousmobility.com/atvcrwd-geoserver/schemas/gml/3.2.1/gml.xsd urn:athena:vcc:crowd:vehicle-events https://develop.vcc.otonomousmobility.com/atvcrwd-geoserver/vehicle-events/wfs?service=WFS&version=2.0.0&request=DescribeFeatureType&typeName=vehicle-events%3AModemState<http://www.opengis.net/wfs/2.0%20https:/develop.vcc.otonomousmobility.com/atvcrwd-geoserver/schemas/wfs/2.0/wfs.xsd%20http:/www.opengis.net/gml/3.2%20https:/develop.vcc.otonomousmobility.com/atvcrwd-geoserver/schemas/gml/3.2.1/gml.xsd%20urn:athena:vcc:crowd:vehicle-events%20https:/develop.vcc.otonomousmobility.com/atvcrwd-geoserver/vehicle-events/wfs?service=WFS&version=2.0.0&request=DescribeFeatureType&typeName=vehicle-events%3AModemState>"> <wfs:member> <null:ModemState gml:id="006ff4c8-7c65-4d2f-89df-4d7fa9afa2ea"> <timestamp>120708750</timestamp> <apn>Context 1 </apn> <basebandModuleFirmwareVersion>20.00.402</basebandModuleFirmwareVersion> <cellId>160081A</cellId> ... <dtg>2018-11-12T09:12:48.014Z</dtg> <geom> <gml:Point srsName="urn:ogc:def:crs:EPSG::4326" srsDimension="2" gml:id="006ff4c8-7c65-4d2f-89df-4d7fa9afa2ea.geom"> <gml:pos>48.67940694 8.97704929</gml:pos> </gml:Point> </geom> </null:ModemState> </wfs:member> ... </wfs:FeatureCollection> The very same problem has already been reported in the past: https://dev.locationtech.org/mhonarc/lists/geomesa-users/msg02330.html I am using the most recent stable versions of GeoMesa (2.2.1), GeoMesa-FS (2.11-2.2.1) and GeoServer (2.14.2) and the issue still persists. Enabling "strict CITE compliance" for WFS in GeoServer and explicitly requesting WFS 1.0.0 in QGIS (as mentioned in the old request linked above) leads to GML 2 being served and is a work-around that fixes the issue for me. However it forces me to use an old WFS version with limited features compared to WFS 2.0.0. Do you know what is the for this? Are there any plans to fix this on your side (not sure whether this is even caused by GeoMesa or GeoServer)? Asked the same question in the geomesa-users list. Thanks and best wishes! Christian Mit freundlichen Grüßen / Kind regards Christian Sickert Crowd Data & Analytics for Automated Driving Daimler AG - Mercedes-Benz Cars Development - RD/AFC +49 176 309 71612 [email protected]<mailto:[email protected]> If you are not the addressee, please inform us immediately that you have received this e-mail by mistake, and delete it. We thank you for your support.
_______________________________________________ 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 [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-users
