Hi Matthias,
I believe this is intended behavior, it's not up to the data store code to
police attribute names
and ids. E.g., if you were just using this layer for WMS, there would not
be any problem,
serving also WFS is your choice, many do, but not everybody.
We have been over this a few times without any good consensus (and more
importantly,
without any funding to take action on it), various positions are:
* Do not allow publishing if the data is not compatible with _all_ services
* Warn the admin if a layer is not compatible with some service restrictions
* Perform on the fly mappings to avoid this issue, with different mappings
per service
The quickest solution for you is probably to setup a sql view that amends
the names and
ids so that they are compliant. This works as long as you don't have to
edit via WFS-T of course.
Cheers
Andrea
On Wed, Jun 15, 2016 at 10:58 AM, Matthias Müller <
[email protected]> wrote:
> Hello everyone,
>
> We are running a Geoserver instance with Postgres/PostGIS backend.
> Everything
> seems to work fine so far, except for WFS with GML.
>
> We have two specific issues here:
>
> 1) The auto-generated feature IDs (see [1]) do not comply with the QName
> convention. We use UUIDs to identify our datasets and Geoserver seems to
> uses
> this UUID directly to generate Feature IDs. Since QNames must not start
> with a
> number, we get invalid GML for roughly 10 out of 16 datasets. Most
> Validators/Clients we have tested fail to parse this GML (QGIS among them).
>
> 2) Geoserver uses Postgres column names as feature attribute names. Since
> Postgres column names are not restricted to QNames (e.g. "12345", "km/s"
> are
> valid column names), we sometimes run into similar issues here.
>
> Is this intended behavior, i.e. is the dataset provider responsible for
> ensuring QName compliant attribute names, or is it a bug?
>
>
> Kind regards,
> Matthias
>
> p.s.: Geoserver version is 2.8.3
>
> [1]:
>
> <gml:featureMember>
> <ckandev:402b28fe-af35-463f-a78f-47f121cea236
> fid="402b28fe-af35-463f-a78f-47f121cea236.1">
> <ckandev:X>51.003874</ckandev:X>
> <ckandev:Y>13.726043</ckandev:Y>
>
> <ckandev:Timestamp>2012-07-20T:10:00GMT+1</ckandev:Timestamp>
> <ckandev:Place>Bannewitz</ckandev:Place>
>
> <ckandev:Zn_1000_-_400___micro_g_per_g_>127.3936706</ckandev:Zn_1000_-_400___micro_g_per_g_>
>
> <ckandev:Zn_400_-_100___micro_g_per_g_>418.9342066</ckandev:Zn_400_-_100___micro_g_per_g_>
>
> <ckandev:Zn_100_-_63___micro_g_per_g_>743.5718278</ckandev:Zn_100_-_63___micro_g_per_g_>
>
> <ckandev:Zn_63_-_0.45___micro_g_per_g_>528.2146161</ckandev:Zn_63_-_0.45___micro_g_per_g_>
>
> <ckandev:Zn_SUMM___micro_g_per_g_>377.8245751</ckandev:Zn_SUMM___micro_g_per_g_>
>
> <ckandev:Cu_1000_-_400___micro_g_per_g_>48.0749849</ckandev:Cu_1000_-_400___micro_g_per_g_>
>
> <ckandev:Cu_400_-_100___micro_g_per_g_>112.1762429</ckandev:Cu_400_-_100___micro_g_per_g_>
>
> <ckandev:Cu_100_-_63___micro_g_per_g_>164.8965903</ckandev:Cu_100_-_63___micro_g_per_g_>
>
> <ckandev:Cu_63_-_0.45___micro_g_per_g_>151.0506145</ckandev:Cu_63_-_0.45___micro_g_per_g_>
>
> <ckandev:Cu_SUMM___micro_g_per_g_>105.0860617</ckandev:Cu_SUMM___micro_g_per_g_>
>
> <ckandev:Cd_1000_-_400___micro_g_per_g_>0.056641806</ckandev:Cd_1000_-_400___micro_g_per_g_>
>
> <ckandev:Cd_400_-_100___micro_g_per_g_>0.166999107</ckandev:Cd_400_-_100___micro_g_per_g_>
>
> <ckandev:Cd_100_-_63___micro_g_per_g_>0.264253773</ckandev:Cd_100_-_63___micro_g_per_g_>
>
> <ckandev:Cd_63_-_0.45___micro_g_per_g_>0.278181578</ckandev:Cd_63_-_0.45___micro_g_per_g_>
>
> <ckandev:Cd_SUMM___micro_g_per_g_>0.1663264</ckandev:Cd_SUMM___micro_g_per_g_>
> <ckandev:Shape>
> <gml:Point srsName="
> http://www.opengis.net/gml/srs/epsg.xml#4326";>
> <gml:coordinates xmlns:gml="
> http://www.opengis.net/gml";
> decimal="." cs="," ts="
> ">13.726043,51.003874</gml:coordinates>
> </gml:Point>
> </ckandev:Shape>
> </ckandev:402b28fe-af35-463f-a78f-47f121cea236>
> </gml:featureMember>
>
>
> ------------------------------------------------------------------------------
> What NetFlow Analyzer can do for you? Monitors network bandwidth and
> traffic
> patterns at an interface-level. Reveals which users, apps, and protocols
> are
> consuming the most bandwidth. Provides multi-vendor support for NetFlow,
> J-Flow, sFlow and other flows. Make informed decisions using capacity
> planning
> reports.
> http://pubads.g.doubleclick.net/gampad/clk?id=1444514421&iu=/41014381
> _______________________________________________
> Geoserver-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/geoserver-users
>
>
--
==
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
*AVVERTENZE AI SENSI DEL D.Lgs. 196/2003*
Le informazioni contenute in questo messaggio di posta elettronica e/o
nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il
loro utilizzo è consentito esclusivamente al destinatario del messaggio,
per le finalità indicate nel messaggio stesso. Qualora riceviate questo
messaggio senza esserne il destinatario, Vi preghiamo cortesemente di
darcene notizia via e-mail e di procedere alla distruzione del messaggio
stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso,
divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od
utilizzarlo per finalità diverse, costituisce comportamento contrario ai
principi dettati dal D.Lgs. 196/2003.
The information in this message and/or attachments, is intended solely for
the attention and use of the named addressee(s) and may be confidential or
proprietary in nature or covered by the provisions of privacy act
(Legislative Decree June, 30 2003, no.196 - Italy's New Data Protection
Code).Any use not in accord with its purpose, any disclosure, reproduction,
copying, distribution, or either dissemination, either whole or partial, is
strictly forbidden except previous formal approval of the named
addressee(s). If you are not the intended recipient, please contact
immediately the sender by telephone, fax or e-mail and delete the
information in this message that has been received in error. The sender
does not give any warranty or accept liability as the content, accuracy or
completeness of sent messages and accepts no responsibility for changes
made after they were sent or for other risks which arise as a result of
e-mail transmission, viruses, etc.
-------------------------------------------------------
------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity planning
reports. http://pubads.g.doubleclick.net/gampad/clk?id=1444514421&iu=/41014381
_______________________________________________
Geoserver-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-users
