Ah, you make a good remark. Indeed I saw the GeoJSON related changes in GeoTools, but GeoServer is using its own encoder for GeoJSON, so yes, not even that format will handle arrays correctly.
Cheers Andrea On Wed, Dec 19, 2018 at 2:46 PM Nugent, Philip J. <nugen...@ornl.gov> wrote: > Hi Andrea, > > > > Thanks for your response. I tested several outputs of WFS and the array > object string ([Ljava.lang.String;@1748e3a9) shows up in GeoJSON as > well. Is the support for encoding to GeoJSON happening at a lower level > outside of WFS? If this is a case, I will look at requesting or > contributing an enhancement if I am able. > > > > Thank you, > > Phil > > > > *From: *Andrea Aime <andrea.a...@geo-solutions.it> > *Reply-To: *"andrea.a...@geo-solutions.it" <andrea.a...@geo-solutions.it> > *Date: *Wednesday, December 19, 2018 at 7:03 AM > *To: *"Nugent, Philip J." <nugen...@ornl.gov> > *Cc: *"geoserver-users@lists.sourceforge.net" < > geoserver-users@lists.sourceforge.net> > *Subject: *Re: [Geoserver-users] String Arrays in PostgreSQL > > > > On Tue, Dec 18, 2018 at 11:11 PM Nugent, Philip J. via Geoserver-users < > geoserver-users@lists.sourceforge.net> wrote: > > The crux of my question is how to represent string data in arrays within > PostgreSQL to utilize the feature for reading and writing from PostGIS > arrays released in version 2.14. As stated in the question, I have created > two columns: one is a character varying array and one is a text array. > When registering the table in GeoServer as a layer, the text array column > doesn’t show up in the feature type details, but the column with character > varying data type does. When trying to access the data via WFS, the > character varying data type data is not serialized as a string, but is > shown as "[Ljava.lang.String;@1748e3a9" for example. Is there additional > configuration needed in GeoServer, such as creating a custom schema, to > handle the serialization of array data from PostgreSQL? > > > > Hi, > > as far as I remember, array support was added at the "low" level, read and > write and the datastore machinery, > > followed by support encoding it out in GeoJSON, but that's it, there was > no follow up on GML (we did not get sponsoring to do that part as well). > > It can still be added of course, see this guide for adding new features in > code: > > > https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer > > > > Cheers > > Andrea > > > > == > > GeoServer Professional Services from the experts! Visit > http://goo.gl/it488V for more information. == Ing. Andrea Aime @geowolf > Technical Lead GeoSolutions S.A.S. Via di Montramito 3/A 55054 Massarosa > (LU) phone: +39 0584 962313 fax: +39 0584 1660272 mob: +39 339 8844549 > http://www.geo-solutions.it http://twitter.com/geosolutions_it > ------------------------------------------------------- *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.* > -- Regards, Andrea Aime == GeoServer Professional Services from the experts! Visit http://goo.gl/it488V for more information. == Ing. Andrea Aime @geowolf Technical Lead GeoSolutions S.A.S. Via di Montramito 3/A 55054 Massarosa (LU) phone: +39 0584 962313 fax: +39 0584 1660272 mob: +39 339 8844549 http://www.geo-solutions.it http://twitter.com/geosolutions_it ------------------------------------------------------- *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.*
_______________________________________________ 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
