Re: [Geoserver-users] Too many namespaces in the GetFeature results
Dear Sebastian, please see my answers bellow: On 08/28/2018 11:22 AM, worldexplorer wrote: Dear Nuno Oliveira, thank you for the answer. It's quite interesting that complex features have this behaviour. Never thought about the fact, that the needed name-spaces are uncertain at the point of the encoding time. To summarize, it affects all encodings of complex features and it's not special on my data. So, adding all name-spaces does not affect the correct visualization of the features? No this not special to your data or schema, and the produced GML document will be valid. This may only become an issue if you have a big number of workspaces \ namespaces (~100) configured in GeoServer, although the produced document will still be valid Best, Sebastian -- Sent from: http://osgeo-org.1560.x6.nabble.com/GeoServer-User-f3786390.html -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ 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 -- Regards, Nuno Oliveira == GeoServer Professional Services from the experts! Visit http://goo.gl/it488V for more information. == Nuno Miguel Carvalho Oliveira @nmcoliveira Software Engineer GeoSolutions S.A.S. Via di Montramito 3/A 55054 Massarosa (LU) Italy phone: +39 0584 962313 fax: +39 0584 1660272 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. -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ 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
Re: [Geoserver-users] Too many namespaces in the GetFeature results
Dear Nuno Oliveira, thank you for the answer. It's quite interesting that complex features have this behaviour. Never thought about the fact, that the needed name-spaces are uncertain at the point of the encoding time. To summarize, it affects all encodings of complex features and it's not special on my data. So, adding all name-spaces does not affect the correct visualization of the features? Best, Sebastian -- Sent from: http://osgeo-org.1560.x6.nabble.com/GeoServer-User-f3786390.html -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ 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
Re: [Geoserver-users] Too many namespaces in the GetFeature results
Hi, When encoding a complex feature we cannot know at encoding time which name-spaces will be needed (a complex feature may chain multiple features from different name-spaces together), so all the available name-spaces are added. Is worth noticing that the produced XML document is valid. This is not something easy to to fix, but with some extra development work it could be done. Regards, Nuno Oliveira On 08/27/2018 10:19 AM, worldexplorer wrote: Dear list, I've noticed a strange thing in my GetFeature request regarding namespaces and I don't know exactly why. When I do a GetFeature request on the default data (e.g. Tasmania state boundaries) of the GeoServer the header looks pretty normal. All necessary namespaces are listed. However, when I query my own data the header includes all namespaces of all configured data of the GeoServer. My configuration on the GeoServer: - I'm working with the App Schema tutorial data → https://github.com/geoserver/geoserver/tree/master/data/app-schema-tutorial/workspaces/tut/tut_RoadSegment - The complex data is stored in a Java Property file which contains Feature information - The data store contains the mapping file of the complex features - The data requires two namespaces (tut and gml) I've compared the outputs of the GetFeature requests from my tutorial data and the default data of the GeoServer (Tasmania state boundaries). You can find both results here: https://docs.google.com/document/d/1utORL9Nk4HByTQAF_OXo_x2gMe0OAqNRYaHZP_cJ5zQ/ Best, Sebastian -- Sent from: http://osgeo-org.1560.x6.nabble.com/GeoServer-User-f3786390.html -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ 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 -- Regards, Nuno Oliveira == GeoServer Professional Services from the experts! Visit http://goo.gl/it488V for more information. == Nuno Miguel Carvalho Oliveira @nmcoliveira Software Engineer GeoSolutions S.A.S. Via di Montramito 3/A 55054 Massarosa (LU) Italy phone: +39 0584 962313 fax: +39 0584 1660272 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. -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ 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
