Geoserver WFS2.0 layer error publishing postgres float list type

GeoServer GeoServer User
,
1

  • GeoServer Version2.28.1 (and 2.26.2)

  • Git Revision80e103e11546c0cf79c52fb36c8c7cdb7bcd5828

  • Build Date24-Nov-2025 18:35

  • GeoTools Version34.1

Postgres table include a field with data type real (float list) generates error during parsing the list. The error is partially embedded in the wfs xml response - see depths field value below:

Partial response is:

wfs:member
<av_demo:LV_Cable_3D gml:id=“LV_Cable_3D.10”>
<av_demo:id>10</av_demo:id>
<av_demo:Diameter>100</av_demo:Diameter>
<av_demo:QL_code>B</av_demo:QL_code>
<av_demo:geom>
<gml:LineString srsName=“http://www.opengis.net/gml/srs/epsg.xml#2193” srsDimension=“3” gml:id=“LV_Cable_3D.10.geom”>
gml:posList1763451.40631793 5914950.70374772 33.4 1763449.47306134 5914951.07394579 33.4 1763450.99498674 5914962.17988794 33.2 1763450.00779189 5914963.53728087 33.2 1763452.02331472 5914979.04446676 33.25 1763455.745862 5915012.25946041 35.4 1763455.86926135 5915013.20552215 35.45 1763432.01205229 5915006.58308998 35.3</gml:posList>
</gml:LineString>
</av_demo:geom>
<av_demo:depths>[Ljava.lang.Float;@1689df0e</av_demo:depths>
</av_demo:LV_Cable_3D>
</wfs:member>

An example request is:

https://registration.augview.net/geoserver/av_demo/ows?service=WFS&version=2.0.0&request=GetFeature&srsname=EPSG:2193&bbox=1763445.9967241,5914969.0689081,1763453.20790121,5914976.2800852,EPSG:2193&typename=av_demo:LV_Cable_3D

Source data as reported by pg_admin is:

“id”,“Diameter”,“QL_code”,“depths”,“geom”
10,100,“B”,“{0.5,0.6,0.75,NULL,0.5,NULL,0.6,0.65}”,"SRID=2193;LINESTRING(1763451 ……

It appears that the list structure is not being correctly parsed.

The WFS2.0 documentation indicates that list types should be supported via nested xml structures.

There may be a Geoserver WFS setting that we have missed. We have not enabled the WFS configuration option labelled ‘Activate complex to simple features conversion’

Any assistance appreciated.

regards

Mike

2

For GeoJSON maybe, but for GML one needs to install and configure either the application schema or the feature templating plugin (for both it’s quite a bit of work, but features templating is a bit easier).

Can you point me to the documentation that states it’s supported out of the box?

Cheers
Andrea

3

Hi. thanks for your response

see section 10.3 or 11.2 of the WFS2.0 standard (Open Geospatial Consortium) for response semantics. I think it should be handled by either a tuple structure or a complex element structure.

I dont think it has anything to do with the spatial concepts of GML or GeoJSON as its just a regular attribute (non-spatial) so should be handled by the regular attribute parsing and xml structuring as defined by the attribute property response.

I will however take a look at feature templating plugin & application schema. Any suggestions for recommended reading please?

regards

Mike